Repository navigation
fix(release-please): bump action to v5.0.0-oce.4 - #36
Merged
Merged
Conversation
v5.0.0-oce.4 bundles the fork's workspace fix. Under separate-pull-requests with node-workspace (or the cargo and maven workspace plugins), release PRs that only bump a dependency were opened without the autorelease: pending label, and their manifest entries landed on another PR. Those PRs were never tagged and the manifest never advanced, so every run opened another one a patch higher; oce-fe-harness is in that loop now. The tag also carries the upstream sync to edce3d8 (js-yaml 4.3.2, xmldom 0.8.15). fix, not ci, so release-please cuts a release that callers can pin. README carries the same hardcoded ref and moves with it. Assisted-by: Claude Code
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.
Points
release-please-reusable.yml, and the README that quotes it, atopenCoreEMR/release-please-action@v5.0.0-oce.4.Why: with
separate-pull-requestsand a workspace plugin, release PRs that only bump a dependency were opened withoutautorelease: pending, and their manifest entries landed on another PR. So they were never tagged, and every run opened another one a patch higher. oce-fe-harness is in that loop now (operator 1.0.2 merged but never tagged; 1.0.3 is open).oce.4bundles the fix (openCoreEMR/release-please#7) and the upstream sync to edce3d8 (openCoreEMR/release-please#8), built in openCoreEMR/release-please-action#3.This is a
fix, not acicommit, so release-please cuts a release that callers can pin.