Skip to content

Conversation

@lgoettgens
Copy link
Member

Follow-up to #1203 with the learnings that I made during the GAP 4.15.0 and 4.15.1 updates.

There are two places where I should add another sentence about how juliainterface is special at that place. I'll do that before we merge this, but I wanted to already open this PR to get some feedback.

@lgoettgens lgoettgens requested a review from fingolfin October 28, 2025 17:14
@codecov
Copy link

codecov bot commented Oct 28, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.56%. Comparing base (afbcd50) to head (d8b7f11).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1281   +/-   ##
=======================================
  Coverage   76.55%   76.56%           
=======================================
  Files          61       61           
  Lines        4901     4902    +1     
=======================================
+ Hits         3752     3753    +1     
  Misses       1149     1149           

see 2 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment on lines 110 to 122
7. In `GAP.jl`, create a PR with the following changes:
1. In the `Project.toml` update the compat bounds as follows:
- `GAP_jll` to the `version` from step 1, with a `~` prefix.
- `GAP_lib_jll` to the `version` from step 3, with a `~` prefix.
- %TODO: `GAP_pkg_juliainterface`
- For each `GAP_pkg_*_jll` package that was updated in step 6, update to the new version
with a `~` prefix. You can find the new version numbers in the registry PRs from step 6.
2. Run `etc/update_artifact.jl` with the new GAP version as argument to the `Artifacts.toml` file.
See the top of that script for instructions.
3. If the GAP release is not ABI-compatible with the previous one, update the minor part of the version
of `GAP.jl` in its `Project.toml`
4. If the GAP release was created from a new release branch (e.g. `stable-4.15` instead of `stable-4.14`),
then update occurrences in `.github/workflows/gap.yml` accordingly.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps we can write a script to take care of most of this, given just the new GAP version? (Not for this PR! just thinking out loud)

@lgoettgens lgoettgens marked this pull request as ready for review November 7, 2025 14:58
@lgoettgens lgoettgens requested a review from fingolfin November 7, 2025 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants