Skip to content

Bump julia-actions/julia-downgrade-compat from 2.6.2 to 2.7.0 - #18

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/julia-actions/julia-downgrade-compat-2.7.0
Open

Bump julia-actions/julia-downgrade-compat from 2.6.2 to 2.7.0#18
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/julia-actions/julia-downgrade-compat-2.7.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 15, 2026

Copy link
Copy Markdown
Contributor

Bumps julia-actions/julia-downgrade-compat from 2.6.2 to 2.7.0.

Release notes

Sourced from julia-actions/julia-downgrade-compat's releases.

v2.7.0

Fixes floors being silently discarded for old-style test layouts.

What was wrong

For a package using the old-style layout — test dependencies in [extras]/[weakdeps] plus [targets].test, with no test/Project.toml — the floors this action resolved were dropped before the tests ran.

The action folds [extras] into the merged [deps], min-resolves, and writes the floors to the project Manifest.toml. But Pkg.test does not run in the project environment: for an old-style layout it synthesizes a sandbox from [deps] plus the [targets].test names via Pkg.Operations.gen_target_project and resolves that fresh. A floor held only for a name reachable through [extras]/[weakdeps] never reached the sandbox, so it installed the newest compatible version instead. allow_reresolve: false did not prevent this.

The downgrade job therefore reported success while testing against current versions rather than the floors.

Impact

Minor rather than patch: downgrade jobs on old-style-layout packages that were passing may now legitimately fail, because they are testing the floors for the first time. That is the intended behaviour — a failure means the declared lower bounds do not actually work.

Consumers pinned to @v2 pick this up automatically.

See #57.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [julia-actions/julia-downgrade-compat](https://github.com/julia-actions/julia-downgrade-compat) from 2.6.2 to 2.7.0.
- [Release notes](https://github.com/julia-actions/julia-downgrade-compat/releases)
- [Changelog](https://github.com/julia-actions/julia-downgrade-compat/blob/main/devdocs/release.md)
- [Commits](julia-actions/julia-downgrade-compat@v2.6.2...v2.7.0)

---
updated-dependencies:
- dependency-name: julia-actions/julia-downgrade-compat
  dependency-version: 2.7.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Aug 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants