Skip to content

Bump prefix-dev/rattler-build-action from 0.2.38 to 0.2.39 - #544

Merged
blooop merged 1 commit into
mainfrom
dependabot/github_actions/prefix-dev/rattler-build-action-0.2.39
Sep 1, 2026
Merged

Bump prefix-dev/rattler-build-action from 0.2.38 to 0.2.39#544
blooop merged 1 commit into
mainfrom
dependabot/github_actions/prefix-dev/rattler-build-action-0.2.39

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 1, 2026

Copy link
Copy Markdown
Contributor

Bumps prefix-dev/rattler-build-action from 0.2.38 to 0.2.39.

Release notes

Sourced from prefix-dev/rattler-build-action's releases.

v0.2.39

What's Changed

✨ New features

⬆️ Dependency updates

Full Changelog: prefix-dev/rattler-build-action@v0.2.38...v0.2.39

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)

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Sep 1, 2026
Bumps [prefix-dev/rattler-build-action](https://github.com/prefix-dev/rattler-build-action) from 0.2.38 to 0.2.39.
- [Release notes](https://github.com/prefix-dev/rattler-build-action/releases)
- [Commits](prefix-dev/rattler-build-action@v0.2.38...v0.2.39)

---
updated-dependencies:
- dependency-name: prefix-dev/rattler-build-action
  dependency-version: 0.2.39
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

@blooop blooop left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

The action's own version is a patch bump, but the substance is what it pins
underneath: rattler-build v0.65.0 → v0.68.0
(prefix-dev/rattler-build-action#115),
three minor versions of the tool that actually builds the package. That is the
part worth reading, and the action's inputs are not where the risk is —
recipe-path and build-args are unchanged.

Read 0.66, 0.67 and 0.68's notes against what this recipe relies on:
--experimental for load_from_file, --no-include-recipe, and
${{ compiler('rust') }} with the variants.yaml floor. All three releases are
additions and fixes — interpreters, late-bound SRC_DIR/PREFIX variables, CRAN
generation, error-message quality. Nothing removed or renamed on any path this
recipe takes, and no breaking-change section in any of the three.

One thing this bump exposes that is worth recording, though it is not a reason to
hold the bump:

CI and publish do not use the same rattler-build. The packaging job's
"conda recipe parses and names the same version" step runs pixi exec rattler-build, which is unpinned and resolves whatever conda-forge currently
offers. conda-publish.yml builds with the action's pin, now v0.68.0. So the
version that proves the recipe renders is not the version that builds it, and
the two drift independently — this PR moves one of them and cannot move the
other. The check passing here is real evidence the recipe is well-formed, just
not evidence about v0.68.0 specifically.

Also worth being explicit: conda-publish.yml only runs off a completed
Auto-publish on main, so PR CI never executes the changed line. The first real
exercise of v0.68.0 will be the next release cut.

@blooop
blooop force-pushed the dependabot/github_actions/prefix-dev/rattler-build-action-0.2.39 branch from 6925f65 to bfbc87b Compare September 1, 2026 12:23
@codecov

codecov Bot commented Sep 1, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.93%. Comparing base (257e523) to head (bfbc87b).

Additional details and impacted files
Flag Coverage Δ
python 42.98% <ø> (ø)
rust 95.22% <ø> (+0.02%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
shipped code (rust) 95.22% <ø> (+0.02%) ⬆️
harness and tooling (python) 42.98% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@blooop
blooop merged commit a946365 into main Sep 1, 2026
15 checks passed
@blooop
blooop deleted the dependabot/github_actions/prefix-dev/rattler-build-action-0.2.39 branch September 1, 2026 12:27
@blooop blooop mentioned this pull request Sep 1, 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.

1 participant