You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's the idea: When a PR is merged that modifies files in deps/src, do this:
get the current version of libsinguliar_julia_jll
increment it (currently by incrementing minor and setting patch to 0
create (or update) a branch oscar-system/libsinguliar (or so) on a fork of the Yggdrasil repo which updates the libsinguliar_julia_jll recipe to use the new master commit, and update to the new version)
(force) push the branch
if no PR for that branch already exists on Yggdrasil, open one (if one exists, the force push will have updated it)
similarly, open or update a PR on Singular.jl with a corresponding change to Project.toml (of course it'll fail initially), and with a link to the Yggdrasil PR in its description
The result still would allow for accidentally making releases without up-to-date libsinguliar_julia_jll but it would make it quite a bit more convenient to do the right thing.
The text was updated successfully, but these errors were encountered:
Here's the idea: When a PR is merged that modifies files in
deps/src
, do this:libsinguliar_julia_jll
minor
and settingpatch
to 0oscar-system/libsinguliar
(or so) on a fork of the Yggdrasil repo which updates thelibsinguliar_julia_jll
recipe to use the newmaster
commit, and update to the new version)Singular.jl
with a corresponding change toProject.toml
(of course it'll fail initially), and with a link to the Yggdrasil PR in its descriptionThe result still would allow for accidentally making releases without up-to-date
libsinguliar_julia_jll
but it would make it quite a bit more convenient to do the right thing.The text was updated successfully, but these errors were encountered: