Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 5, 2026

Bumps insta from 1.45.0 to 1.46.0.

Release notes

Sourced from insta's releases.

1.46.0

Release Notes

  • Add INSTA_PENDING_DIR environment variable for Bazel and other hermetic build systems. When set, pending snapshots are written to a separate directory while keeping the source tree read-only. We are very open to feedback on this feature. #852
  • Fix documentation for test.runner_fallback config key. #853

Install cargo-insta 1.46.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mitsuhiko/insta/releases/download/1.46.0/cargo-insta-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/mitsuhiko/insta/releases/download/1.46.0/cargo-insta-installer.ps1 | iex"

Download cargo-insta 1.46.0

File Platform Checksum
cargo-insta-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
cargo-insta-x86_64-apple-darwin.tar.xz Intel macOS checksum
cargo-insta-x86_64-pc-windows-msvc.zip x64 Windows checksum
cargo-insta-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum
cargo-insta-x86_64-unknown-linux-musl.tar.xz x64 MUSL Linux checksum

1.45.1

Release Notes

  • Fix backward compatibility with TOML format produced by insta < 1.45.0. #849 (@​chitoku-k)

Install cargo-insta 1.45.1

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mitsuhiko/insta/releases/download/1.45.1/cargo-insta-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/mitsuhiko/insta/releases/download/1.45.1/cargo-insta-installer.ps1 | iex"

Download cargo-insta 1.45.1

... (truncated)

Changelog

Sourced from insta's changelog.

1.46.0

  • Add INSTA_PENDING_DIR environment variable for Bazel and other hermetic build systems. When set, pending snapshots are written to a separate directory while keeping the source tree read-only. We are very open to feedback on this feature. #852
  • Fix documentation for test.runner_fallback config key. #853

1.45.1

  • Fix backward compatibility with TOML format produced by insta < 1.45.0. #849 (@​chitoku-k)
Commits
  • 7d27e3a Release 1.46.0 (#855)
  • 3aa59d6 Add INSTA_PENDING_DIR environment variable for hermetic builds (#852)
  • fd40cf7 Fix docs for test.runner_fallback config key (#853)
  • ac191ba Add test for multiline snapshots without special characters (#848)
  • 55f6999 Release 1.45.1 (#850)
  • 00b1cd4 Fix backward compatibility with TOML format produced by insta < 1.45.0 (#849)
  • See full diff in compare view

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @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)

@Dandandan Dandandan added this pull request to the merge queue Jan 5, 2026
Merged via the queue into main with commit 52bbc8a Jan 5, 2026
59 checks passed
@dependabot dependabot bot deleted the dependabot/cargo/main/insta-1.46.0 branch January 5, 2026 09:51
github-merge-queue bot pushed a commit that referenced this pull request Jan 11, 2026
## Which issue does this PR close?

<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax. For example
`Closes #123` indicates that this PR will close issue #123.
-->

- N/A

## Rationale for this change

<!--
Why are you proposing this change? If this is already explained clearly
in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->

Occasionally we do PRs to bump a bunch of versions in `Cargo.lock`,
recent example:

- #19667

Ideally this should be handled by dependabot already. I suspect the
default limit of 5 is preventing dependabot from creating all the PRs it
needs; this causes it to error and those version bumps are "lost".

- I say "lost" but dependabot can pick it up on the next run... if it
doesn't error again

See an example from a dependabot run:

<img width="703" height="118" alt="image"
src="https://github.com/user-attachments/assets/f8ae6b70-6fe1-4613-8c60-28564c23188b"
/>

From the logs:

```text
 +-------------------------------------------------------+
|          Changes to Dependabot Pull Requests          |
+---------+---------------------------------------------+
| created | insta ( from 1.45.0 to 1.46.0 )             |
| created | tracing ( from 0.1.43 to 0.1.44 )           |
| created | syn ( from 2.0.111 to 2.0.113 )             |
| created | async-compression ( from 0.4.35 to 0.4.36 ) |
| created | object_store ( from 0.12.4 to 0.13.0 )      |
| created | serde_json ( from 1.0.145 to 1.0.148 )      |
| created | bigdecimal ( from 0.4.9 to 0.4.10 )         |
| created | clap ( from 4.5.53 to 4.5.54 )              |
| created | libc ( from 0.2.177 to 0.2.179 )            |
| created | tokio ( from 1.48.0 to 1.49.0 )             |
| created | tokio-util ( from 0.7.17 to 0.7.18 )        |
| created | sqllogictest ( from 0.28.4 to 0.29.0 )      |
+---------+---------------------------------------------+
```

We expect to have all these PRs created (this was for the run 5 days
ago), but only these were created on that day:

- #19645
- #19644
- #19643

And considering these PRs were still open at the time:

- #19544
- #19325

We can see it hit the 5 limit.

> Dependabot default behavior:
>
> - If five pull requests with version updates are open, no further pull
requests are raised until some of those open requests are merged or
closed.
> - Security updates have a separate, internal limit of ten open pull
requests which cannot be changed.

-
https://docs.github.com/en/code-security/dependabot/working-with-dependabot/dependabot-options-reference#open-pull-requests-limit-

## What changes are included in this PR?

<!--
There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->

Bump the limit to 15. We might have an appetite for increasing it more,
15 was chosen arbitrarily.

## Are these changes tested?

<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->

Dependabot only.

## Are there any user-facing changes?

<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->

No.

<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant