Repository navigation
chore(release): drop the release-as pin for packages/emulate - #63
Conversation
0.4.1 is published. While `release-as: 0.4.1` stays set, every later release of @pleaseai/emulate would try 0.4.1 again.
Up to standards ✅🟢 Issues
|
There was a problem hiding this comment.
No issues found across 1 file
You’re at about 95% of the monthly reviewed-line limit. You may want to disable incremental reviews to conserve quota. Reviews will continue until that limit is exceeded. If you need help avoiding interruptions, please contact contact@cubic.dev.
|
[Low impact] The change appears safe to merge. SummaryRemoves the fixed
Reviews (1) · Last reviewed commit: "chore(release): drop the release-as pin ..." · Reviewed by Greptile |



Summary
Removes the
release-as: 0.4.1pin that #61 added forpackages/emulate. 0.4.1 is now published (#62, release run 41045652183). While the pin is set, every later release of@pleaseai/emulatewould try 0.4.1 again.After this change,
release-please-config.jsonis byte-identical to its state before #61 (blobbdfbb36).This is a
chorecommit that touches no package path, so it does not trigger a release.Verification
git diffshows only thepackages/emulateentry going back to{}..release-please-manifest.jsonalready recordspackages/emulateat0.4.1, so the nextfix/featcommit to the package bumps from 0.4.1 as usual.Related issue
Follow-up to #61 and #62.
Checklist
Summary by cubic
Drops the
release-as: 0.4.1pin forpackages/emulateso the nextfixorfeatcommit to the package bumps from the already-published 0.4.1 instead of trying to release 0.4.1 again. The config returns to its state before the pin was added, and thischorecommit does not trigger a release.Written for commit 3d3f9fe. Summary will update on new commits.