Conversation
Overleaf git *write* is a premium-only feature. Gating the PyPI publish (release.yml) and every PR (tests.yml real-overleaf job) on a live, paid third-party credential made CI brittle: when the Overleaf premium plan lapsed, pushes to the test project began returning HTTP 403, which silently blocked the v0.4.0 release (tagged but never published) and turned the nightly canary red. Decouple the paid dependency from the gates: - release.yml: drop `needs: acceptance` from `build` and mark the acceptance job `continue-on-error`, so a write-403 can no longer stop a publish. It still runs as a release-moment signal. - tests.yml: mark the `real-overleaf` job `continue-on-error` so the same failure is informational, not a red X on every PR. Both live-Overleaf jobs auto-resume as useful green signals once write access is restored. nightly.yml remains the dedicated daily canary. To reinstate a hard release gate, re-add `needs: acceptance` and drop `continue-on-error`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-Authored-By: amcheste <13696614+amcheste@users.noreply.github.com>
…f-write-tests ci: stop gating releases/PRs on the live Overleaf write suite
v0.4.0 was tagged 2026-05-12 but never reached PyPI: the release pipeline was gated on a live Overleaf write test, and the test project's premium plan had lapsed (writes return HTTP 403), which blocked the publish. With that gate removed (PR #39), 0.4.1 ships all of 0.4.0's changes plus the CI fixes — it's the first published release of the 0.4.x line. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-Authored-By: amcheste <13696614+amcheste@users.noreply.github.com>
chore: release v0.4.1 (+ develop↔main sync)
amcheste
approved these changes
May 27, 2026
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.
Summary
Promotes the merged v0.4.1 work from
developtomain— the last step before tagging and publishing.developnow contains everything: themain→developsync (dependabot + release commits), the CI decoupling (#39), and thechore: release v0.4.1bump (#46). This brings it all tomainso thev0.4.1tag can be cut frommain.Merge + publish (yours — the bot can't push to
mainor push tags)--adminis needed becausemainhasenforce_admins.latest.Verify after
v0.4.1is green (acceptance job soft-fails, build + publish succeed).pip install overleaf-mcp-serverresolves to0.4.1.🤖 Generated with Claude Code