CI: add release branch testing and documentation workflows#321
Merged
CI: add release branch testing and documentation workflows#321
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #321 +/- ##
=======================================
Coverage 62.99% 62.99%
=======================================
Files 52 52
Lines 4402 4402
=======================================
Hits 2773 2773
Misses 1629 1629
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
b12cc76 to
70c1aca
Compare
Add comprehensive CI support for the release branch: - Add vendor-deps.jl.yml: Tests vendored environment by running vendor-deps.jl on the current branch and executing tests - Add release.yml: Runs tests and deploys documentation for the release branch (documentation available at /release/ URL) - Update existing workflows to use branches-ignore for release branch PRs, ensuring only release.yml runs for release-targeted PRs - Update docs/make.jl to support DOCUMENTER_DEVBRANCH environment variable for configurable devbranch and devurl Written by Claude
70c1aca to
3d16f6e
Compare
The vendor-deps.jl script uses `git show branch:file` to fetch Project.toml, which requires the branch to exist locally. In CI with shallow clone, we need to fetch the branch first and use the `origin/` prefix.
67a28ea to
432dbfc
Compare
Without this flag, `Pkg.update()` was updating the global environment instead of the JETLS project, causing JETLS to not be found.
Add --local flag to use local path references in [sources] instead of GitHub URL+rev. This allows testing the vendored environment in CI and local development where the vendor/ directory is generated but not committed to the repository. - Without --local: uses url+subdir+rev (for release branch commits) - With --local: uses path (for CI testing and local development) Written by Claude
dd5c06e to
a7ebfc5
Compare
After vendoring, the Manifest.toml contains UUIDs from before the rewrite, causing Pkg operations to fail with "could not find manifest entry for package with uuid". Fix by cleaning manifest files and running Pkg.instantiate() after vendoring completes. Written by Claude
aviatesk
added a commit
that referenced
this pull request
Nov 25, 2025
aviatesk
added a commit
that referenced
this pull request
Nov 25, 2025
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.
Add comprehensive CI support for the release branch:
Written by Claude