Update Curvenote installation to latest version#49
Open
stevejpurves wants to merge 2 commits intomainfrom
Open
Update Curvenote installation to latest version#49stevejpurves wants to merge 2 commits intomainfrom
stevejpurves wants to merge 2 commits intomainfrom
Conversation
|
Curvenote Preview You may test this pull request by updating your action: ...
jobs:
publish:
uses: curvenote/actions/.github/workflows/publish.yml@PR49
with:
... |
fwkoch
approved these changes
Dec 18, 2025
fwkoch
reviewed
Dec 18, 2025
| "name": "@curvenote/actions", | ||
| "private": true, | ||
| "version": "1.0.16", | ||
| "version": "1.0.17", |
Member
There was a problem hiding this comment.
You need to explicitly update the version, but then it should just publish on merge to main.
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
2 participants
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.
It explicitly installs the latest tag instead of just having it unpinned, which you should usually do what we want, but also gives us an additional level of control in terms of what gets pulled in on CI because we can move this latest tag to avoid issues on npm.