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

Update fun-stack-backend, ... to 0.9.21 #465

Conversation

scala-steward
Copy link
Contributor

@scala-steward scala-steward commented Nov 23, 2023

About this PR

📦 Updates

  • io.github.fun-stack:fun-stack-backend
  • io.github.fun-stack:fun-stack-lambda-http-api-tapir
  • io.github.fun-stack:fun-stack-lambda-http-rpc
  • io.github.fun-stack:fun-stack-lambda-ws-event-authorizer
  • io.github.fun-stack:fun-stack-lambda-ws-rpc

from 0.8.9 to 0.9.21

Usage

Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "io.github.fun-stack" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.github.fun-stack" }
}]
labels: library-update, early-semver-major, semver-spec-minor, commit-count:1

@scala-steward scala-steward force-pushed the update/fun-stack-backend-0.9.21 branch from e4572d1 to 0f3d9ac Compare December 7, 2023 16:06
@scala-steward
Copy link
Contributor Author

Superseded by #482.

@scala-steward scala-steward deleted the update/fun-stack-backend-0.9.21 branch January 12, 2024 20:13
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