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

chore(deps): Update dependency net.neoforged:neoforge to v21.3.10-beta #170

Merged
merged 1 commit into from
Nov 3, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 2, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
net.neoforged:neoforge 21.3.4-beta -> 21.3.10-beta age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

NeoForged/NeoForge (net.neoforged:neoforge)

v21.3.5-beta

Compare Source


Configuration

📅 Schedule: Branch creation - "after 5pm on the 2nd day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

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

@renovate renovate bot changed the title chore(deps): Update dependency net.neoforged:neoforge to v21.3.8-beta chore(deps): Update dependency net.neoforged:neoforge to v21.3.10-beta Nov 3, 2024
@zml2008 zml2008 self-assigned this Nov 3, 2024
@zml2008 zml2008 added this to the 6.1.1 milestone Nov 3, 2024
@zml2008 zml2008 merged commit da6dd7d into mc/1.21 Nov 3, 2024
2 checks passed
@zml2008 zml2008 deleted the renovate/neoforge branch November 3, 2024 03:21
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