feat: npm publish main if package version changes #30
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
✅ Deploy Preview for oslmap ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
netlify failed because github was dead at the time |
johnrees
force-pushed
the
jr/auto-publish-npm
branch
from
1b3ceb0 to
7d47004
Compare
|
closing in favour of #135 but happy to pursue this route instead if you think it's better @jessicamcinchak |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently set to dry-run for testing. I'm not sure if it'll like pnpm yet. GitHub is being weird too so I'll try this out tomorrow.
In theory we can keep merging to main as we are, then when we want to create a release, we create a PR that bumps the package version number (and any CHANGELOG updates) and it'll then auto publish on merge.