You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
This PR replaces semantic-release with Changesets - this is the Guardian's recommended approach to automated NPM releases.
How to test
Create a patch release by running npm run release and following the instructions.
When this PR is merged it the Changesets bot (once installed) will create a subsequent release PR. Once this second PR is merged the release will be complete.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Wonderful, thanks for doing this! Added a couple of minor questions.
#2080 is waiting to be merged, maybe that can be used to test the new process?
Yeah definitely, I think if this all works (which it should) we'd just need to add a changeset to the other pr using the changesets cli tool and it would make a great test.
Since the migration to changesets from semantic-release in #2071,
the requirement to use convential commits is removed.
Therefore we can drop a dependency.
Since the migration to changesets from semantic-release in #2071,
the requirement to use convential commits is removed.
Therefore we can drop a dependency.
Since the migration to changesets from semantic-release in #2071,
the requirement to use convential commits is removed.
Therefore we can drop a dependency.
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.
joecowton1
force-pushed
the
jc/test-changeset
branch
2 times, most recently
from
What does this change?
This PR replaces semantic-release with Changesets - this is the Guardian's recommended approach to automated NPM releases.
How to test
Create a patch release by running
npm run releaseand following the instructions.When this PR is merged it the Changesets bot (once installed) will create a subsequent release PR. Once this second PR is merged the release will be complete.