This repository has been archived by the owner on Nov 4, 2024. It is now read-only.
feat: release monodeploy v3.0.0 #450
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## main #450 +/- ##
==========================================
- Coverage 96.27% 95.10% -1.18%
==========================================
Files 43 51 +8
Lines 1154 1368 +214
Branches 249 311 +62
==========================================
+ Hits 1111 1301 +190
- Misses 43 67 +24 |
Monodeploy Publish PreviewThis Pull Request introduces the following changes: |
BREAKING CHANGE: Change the default of the 'access' config option from public to infer. This reduces risk of accidental publish of private packages. The infer option respects the user's yarnrc.yml config, as well as publishConfig.access manifest field.
added 2 commits
December 18, 2021 16:45
BREAKING CHANGE: Monodeploy no longer tags the commit containing the code changes, but rather tags the later commit which contains the package.json changes and other publish artifacts. This is more inline with how Lerna operates and means the tag will match the version in the package.json, as well as the changelog files. If there is interest in adding back the old behaviour behind a configuration option, please open a GitHub issue.
This introduces the 'packageGroupManifestField' config option to create groups of packages based on a common field in each workspace manifest (package.json). All packages within a group will have the same version strategy and version number at publish time, and will be grouped under a single git tag and single release (under the GitHub plugin).
* fix: prereleaseNPMTag cli argument was not being read BREAKING CHANGE: Array CLI argument syntax has changed due to the migration from yargs to clipanion. Instead of '--plugins plugin-a plugin-b', the new syntax is to specify the cli flag per item to yield '--plugins plugin-a --plugins plugin-b'.
added 10 commits
December 25, 2021 21:16
chore: merge main into next/3.0.0
* feat: support for config presets * feat: monodeploy will auto-detect your monodeploy.config.js file
BREAKING CHANGE: Private workspaces are now no longer pruned prior to dependency graph traversal and when considering version strategies for a group. This means you can create a private workspace as a devDependency of other packages and updates to that private workspace will propagate to the dependents with the correct version strategy -- assuming all these packages are in the same group. The private package, although considered when determining the version strategy, is not published.
BREAKING CHANGE: Monodeploy will now publish the top level workspace if not marked as private, and if a change is detected. This means monodeploy can now be used to publish non-monorepos.
* refactor: extract patchPackageJSON from applyReleases * refactor: move patch manifest step closer to publish * refactor: split changeset generation from file creation * refactor: derive workspaces to publish directly from changeset * feat: deprecate --prepend-changelog in favour of --changelog-filename * feat: add --apply-changeset cli flag
added 3 commits
April 7, 2022 14:41
This fixes a bug in an earlier v3.0.0 release candidate, where it was possible for monodeploy to publish a new version of a group with a value smaller than the latest release. This also addresses issues around non-idiomatic versioning. So a major version strategy is now guaranteed to yield x.0.0, while minor is guaranteed to yield x.x.0. This guarantee regressed in an earlier release candidate, and was incorrectly believed to be correct behaviour. The test coverage covering this functionality has been updated with comments.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Github Releases for the changelog.