Repository navigation
chore: version packages - #29
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@eisbachcode/emdash-plugin-analytics@0.3.0
Minor Changes
3b07523: Requires EmDash 1.0.1 or later. Both the peer dependency and the manifest's
env:emdashrequirement are now>=1.0.1, so EmDash refuses to install this version from the registry on an older site.On EmDash 0.39 to 0.42, stay on 0.2.x, which keeps working there. To move to this version, update EmDash to 1.0.1 first, then the plugin. With pnpm, installing it on an older site only warns about the peer dependency; with npm 7 or later, the install fails with
ERESOLVE. An existing^0.2.xrange never resolves to 0.3.0, so no install moves on its own.The plugin's behaviour and stored data are the same as in 0.2.4.