Repository navigation
fix: align release-please manifest with latest tag v0.3.0 - #128
Open
mattdjenkinson wants to merge 1 commit into
Open
mattdjenkinson wants to merge 1 commit into
mattdjenkinson wants to merge 1 commit into
Conversation
v0.3.0 was published by hand, so the manifest (0.2.11) is behind the latest tag and the Release Please workflow fails its manifest check on the next push to main. Set the manifest, package.json and package-lock.json to 0.3.0 so the next release is cut from there.
mattdjenkinson
enabled auto-merge
November 11, 2026 17:07
mattdjenkinson
requested review from
AriaEdo,
felixwidjaja,
gaghan430 and
yahyafakhroji
November 11, 2026 17:07
This branch has not been deployed
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
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.
Summary
main..release-please-manifest.json,package.jsonandpackage-lock.jsonto 0.3.0 so the next release is cut from there.v0.3.0 itself is already live: because the hand-published release did not trigger the deploy, it was deployed with a manual run of the Deploy Datum Compute workflow from the tag.
Test plan
mainpasses after merge