Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump flipper-active_record from 1.3.0 to 1.3.1 #6030

Merged
merged 1 commit into from
Oct 1, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 9, 2024

Bumps flipper-active_record from 1.3.0 to 1.3.1.

Release notes

Sourced from flipper-active_record's releases.

v1.3.1

What's Changed

New Contributors

Full Changelog: flippercloud/flipper@v1.3.0...v1.3.1

Commits
  • 4b911dd Release 1.3.1
  • 873418a Cowboy code a default stub for telemetry
  • 91e1e43 Merge pull request #868 from flippercloud/dependabot/github_actions/superchar...
  • 18cccb9 Merge pull request #881 from flippercloud/active-record-poisoned-transaction
  • 0a38a46 require new transaction for add/set as well
  • 1c9e0a2 Use requires_new with transaction to avoid poisoning
  • 8695db3 Correct spelling
  • 110820b Silence more stuff
  • 028a9bb Update fail_on_output to use capture_output when checking
  • 16988d9 Fix failing spec due to deprecation warning
  • Additional commits viewable 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)

Bumps [flipper-active_record](https://github.com/flippercloud/flipper) from 1.3.0 to 1.3.1.
- [Release notes](https://github.com/flippercloud/flipper/releases)
- [Changelog](https://github.com/flippercloud/flipper/blob/main/Changelog.md)
- [Commits](flippercloud/flipper@v1.3.0...v1.3.1)

---
updated-dependencies:
- dependency-name: flipper-active_record
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Sep 9, 2024
@dependabot dependabot bot added the ruby Pull requests that update Ruby code label Sep 9, 2024
@elasticspoon elasticspoon merged commit 116951b into main Oct 1, 2024
18 checks passed
@elasticspoon elasticspoon deleted the dependabot/bundler/flipper-active_record-1.3.1 branch October 1, 2024 03:59
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 ruby Pull requests that update Ruby code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants