Skip to content

Commit

Permalink
Release v4.2.0
Browse files Browse the repository at this point in the history
  • Loading branch information
jeremystretch committed Jan 6, 2025
1 parent b761097 commit 9d82a66
Show file tree
Hide file tree
Showing 14 changed files with 66,929 additions and 61,599 deletions.
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/01-feature_request.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ body:
attributes:
label: NetBox version
description: What version of NetBox are you currently running?
placeholder: v4.1.11
placeholder: v4.2.0
validations:
required: true
- type: dropdown
Expand Down
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/02-bug_report.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ body:
attributes:
label: NetBox Version
description: What version of NetBox are you currently running?
placeholder: v4.1.11
placeholder: v4.2.0
validations:
required: true
- type: dropdown
Expand Down
8 changes: 1 addition & 7 deletions docs/development/release-checklist.md
Original file line number Diff line number Diff line change
Expand Up @@ -120,15 +120,9 @@ Then, compile these portable (`.po`) files for use in the application:
* Update the example version numbers in the feature request and bug report templates under `.github/ISSUE_TEMPLATES/`.
* Replace the "FUTURE" placeholder in the release notes with the current date.

Commit these changes to the `main` branch and push upstream.

### Verify CI Build Status

Ensure that continuous integration testing on the `main` branch is completing successfully. If it fails, take action to correct the failure before proceeding with the release.

### Submit a Pull Request

Submit a pull request titled **"Release vX.Y.Z"** to merge the current release branch (e.g. `release-vX.Y.Z`) into `main`. Copy the documented release notes into the pull request's body.
Commit the above changes and submit a pull request titled **"Release vX.Y.Z"** to merge the current release branch (e.g. `release-vX.Y.Z`) into `main`. Copy the documented release notes into the pull request's body.

Once CI has completed and a colleague has reviewed the PR, merge it. This effects a new release in the `main` branch.

Expand Down
5 changes: 1 addition & 4 deletions docs/release-notes/version-4.2.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,6 @@
# NetBox v4.2

## v4.2-beta1 (2024-12-02)

!!! danger "Not for Production Use"
This is a beta release of NetBox intended for testing and evaluation. **Do not use this software in production.** Also be aware that no upgrade path is provided to future releases.
## v4.2.0 (2025-01-06)

### Breaking Changes

Expand Down
1 change: 1 addition & 0 deletions mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -176,6 +176,7 @@ nav:
- Provider Network: 'models/circuits/providernetwork.md'
- Virtual Circuit: 'models/circuits/virtualcircuit.md'
- Virtual Circuit Termination: 'models/circuits/virtualcircuittermination.md'
- Virtual Circuit Type: 'models/circuits/virtualcircuittype.md'
- Core:
- DataFile: 'models/core/datafile.md'
- DataSource: 'models/core/datasource.md'
Expand Down
Loading

0 comments on commit 9d82a66

Please sign in to comment.