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

Bump org.json4s:json4s-ast_2.10 from 3.2.10 to 3.6.12 #116

Merged
merged 3 commits into from Feb 21, 2023

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 20, 2023

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.


Bumps org.json4s:json4s-ast_2.10 from 3.2.10 to 3.6.12.

Commits
  • 32f4865 Setting version to 3.6.12
  • 7e3eec0 Update scala-library to 2.13.7 in 3.6
  • 361114d Update scala-steward.yml
  • 584c32b Update joda-time to 2.10.13 in 3.6
  • 3b44c80 Update .scala-steward.conf
  • 4eacead add explicit types for implicits
  • ddbf933 Update sbt to 1.4.9 in 3.6
  • debda8f Update sbt-sonatype to 3.9.10 in 3.6
  • 7abcaef Update .scala-steward.conf
  • 305bc15 ignore scala-xml update
  • 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 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 [org.json4s:json4s-ast_2.10](https://github.com/json4s/json4s) from 3.2.10 to 3.6.12.
- [Release notes](https://github.com/json4s/json4s/releases)
- [Commits](json4s/json4s@v3.2.10...v3.6.12)

---
updated-dependencies:
- dependency-name: org.json4s:json4s-ast_2.10
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/gradle/org.json4s-json4s-ast_2.10-3.6.12 branch from f29ac31 to b947833 Compare February 20, 2023 23:30
dependabot bot and others added 2 commits February 20, 2023 23:33
Signed-off-by: dependabot[bot] <support@github.com>
@harshavamsi harshavamsi merged commit e40d44a into main Feb 21, 2023
@dependabot dependabot bot deleted the dependabot/gradle/org.json4s-json4s-ast_2.10-3.6.12 branch February 21, 2023 00:03
@opensearch-trigger-bot
Copy link

The backport to 1.0 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-1.0 1.0
# Navigate to the new working tree
pushd ../.worktrees/backport-1.0
# Create a new branch
git switch --create backport/backport-116-to-1.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e40d44a111d343f68ab2635fc41e865de2b6df15
# Push it to GitHub
git push --set-upstream origin backport/backport-116-to-1.0
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-1.0

Then, create a pull request where the base branch is 1.0 and the compare/head branch is backport/backport-116-to-1.0.

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.

None yet

1 participant