Skip to content

chore: Configure Renovate#2

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/configure
Open

chore: Configure Renovate#2
renovate[bot] wants to merge 1 commit intomainfrom
renovate/configure

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Apr 16, 2026

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


Detected Package Files

  • native/javex_nif/Cargo.toml (cargo)
  • .github/workflows/ci.yml (github-actions)
  • .github/workflows/release.yml (github-actions)
  • mise.toml (mise)
  • mix.exs (mix)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title

What to Expect

With your current configuration, Renovate will create 13 Pull Requests:

chore(deps): update dependency elixir to v1.19.5
  • Schedule: ["at any time"]
  • Branch name: renovate/elixir-1.x
  • Merge into: main
  • Upgrade elixir to 1.19.5
fix(deps): update rust crate deterministic-wasi-ctx to v4.0.1
  • Schedule: ["at any time"]
  • Branch name: renovate/deterministic-wasi-ctx-4.x
  • Merge into: main
  • Upgrade deterministic-wasi-ctx to =4.0.1
chore(deps): update dependency rust to v1.95.0
  • Schedule: ["at any time"]
  • Branch name: renovate/rust-1.x
  • Merge into: main
  • Upgrade rust to 1.95.0
fix(deps): update rust crate sha2 to 0.11
  • Schedule: ["at any time"]
  • Branch name: renovate/sha2-0.x
  • Merge into: main
  • Upgrade sha2 to 0.11
fix(deps): update rust crate wasmparser to 0.246
  • Schedule: ["at any time"]
  • Branch name: renovate/wasmparser-0.x
  • Merge into: main
  • Upgrade wasmparser to 0.246
chore(deps): update actions/cache action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-cache-5.x
  • Merge into: main
  • Upgrade actions/cache to v5
chore(deps): update actions/checkout action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-6.x
  • Merge into: main
  • Upgrade actions/checkout to v6
chore(deps): update dependency ubuntu to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/ubuntu-24.x
  • Merge into: main
  • Upgrade ubuntu to 24.04
chore(deps): update github artifact actions (major)
chore(deps): update jdx/mise-action action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/jdx-mise-action-4.x
  • Merge into: main
  • Upgrade jdx/mise-action to v4
chore(deps): update softprops/action-gh-release action to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/softprops-action-gh-release-3.x
  • Merge into: main
  • Upgrade softprops/action-gh-release to v3
fix(deps): update rust crate wasmtime to v43
  • Schedule: ["at any time"]
  • Branch name: renovate/wasmtime-43.x
  • Merge into: main
  • Upgrade wasmtime to 43
fix(deps): update rust crate wasmtime-wasi to v43
  • Schedule: ["at any time"]
  • Branch name: renovate/wasmtime-wasi-43.x
  • Merge into: main
  • Upgrade wasmtime-wasi to 43

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.


❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


This PR was generated by Mend Renovate. View the repository job log.

pepicrft pushed a commit that referenced this pull request Apr 16, 2026
Replace the tag-triggered model with one where:

- The workflow runs on every push to main (and workflow_dispatch
  for manual overrides).
- A `decide` job uses `git-cliff --bumped-version` to compute the
  next semver from conventional commits since the last tag. If
  there are no releasable commits, every downstream job is
  skipped via `if: needs.decide.outputs.release == 'true'`.
- The `release` job runs every reversible step first — bump
  mix.exs, write the checksum file from the freshly-built
  artifacts, pre-seed the rustler_precompiled cache so hex
  publish can compile without a GitHub release existing yet,
  generate notes — and only then enters the irreversible block:

    1. mix hex.publish (cannot be undone after 24h)
    2. git push --atomic origin main vX.Y.Z (with rebase retry)
    3. softprops/action-gh-release@v2 (cosmetic, easiest to fix)

  If anything before #1 fails, nothing leaks. If #1 succeeds and
  #2 races, we rebase and retry. If #3 fails, hex + tag are
  already in place; the GitHub release can be created by hand.

The `chore(release): vX.Y.Z` commit pushed by the workflow uses
the default GITHUB_TOKEN, which by design does not retrigger
workflows — no [skip ci] needed.

workflow_dispatch supports a forced version input for emergency
or out-of-band releases.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.

0 participants