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

Prepare for Netbox 4.2 #1368

Merged
merged 1 commit into from
Jan 7, 2025

Conversation

tobiasge
Copy link
Member

@tobiasge tobiasge commented Jan 7, 2025

Related Issue: -

New Behavior

  • Update compose file for Netbox 4.2
  • Update Nginx Unit to latest release
  • Use new branch names from Netbox repository

Contrast to Current Behavior

Discussion: Benefits and Drawbacks

  • None

Changes to the Wiki

  • None

Proposed Release Note Entry

  • Update Nginx Unit to latest release

Double Check

  • I have read the comments and followed the PR template.
  • I have explained my PR according to the information in the comments.
  • My PR targets the develop branch.

@tobiasge tobiasge requested a review from cimnine January 7, 2025 06:37
@cimnine
Copy link
Collaborator

cimnine commented Jan 7, 2025

How is latest tagged like this?

@tobiasge
Copy link
Member Author

tobiasge commented Jan 7, 2025

Its done with the version tags: https://github.com/netbox-community/netbox-docker/pull/1368/files#diff-4d2a8eefdf2a9783512a35da4dc7676a66404b6f3826a8af9aad038722da6823L290

@tobiasge
Copy link
Member Author

tobiasge commented Jan 7, 2025

This is only as a reminder for me: PR required checks need to be changed for the new branch names.

@tobiasge tobiasge merged commit 11615df into netbox-community:develop Jan 7, 2025
9 checks passed
@tobiasge tobiasge deleted the prepare-netbox-4.2 branch January 7, 2025 07:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants