Skip to content

Conversation

oarbusi
Copy link
Collaborator

@oarbusi oarbusi commented Oct 1, 2025

Description

This should have happened automatically when releasing 1.41.1 but was done in the wrong branch, master. Fixed in #3734 and this brings the changes into master-v1.

Link to any related issue(s):

Type of change:

  • Bug fix (non-breaking change which fixes an issue). Please, add the "bug" label to the PR.
  • New feature (non-breaking change which adds functionality). Please, add the "enhancement" label to the PR. A migration guide must be created or updated if the new feature will go in a major version.
  • Breaking change (fix or feature that would cause existing functionality to not work as expected). Please, add the "breaking change" label to the PR. A migration guide must be created or updated.
  • This change requires a documentation update
  • Documentation fix/enhancement

Required Checklist:

  • I have signed the MongoDB CLA
  • I have read the contributing guides
  • I have checked that this change does not generate any credentials and that they are NOT accidentally logged anywhere.
  • I have added tests that prove my fix is effective or that my feature works per HashiCorp requirements
  • I have added any necessary documentation (if appropriate)
  • I have run make fmt and formatted my code
  • If changes include deprecations or removals I have added appropriate changelog entries.
  • If changes include removal or addition of 3rd party GitHub actions, I updated our internal document. Reach out to the APIx Integration slack channel to get access to the internal document.

Further comments

@oarbusi oarbusi marked this pull request as ready for review October 1, 2025 13:25
@oarbusi oarbusi requested review from a team as code owners October 1, 2025 13:25
@Copilot Copilot AI review requested due to automatic review settings October 1, 2025 13:25
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Updates the CHANGELOG.md and documentation to reflect the v1.41.1 release by adding the appropriate changelog entries and updating the example link reference to point to the correct version tag.

  • Adds CHANGELOG.md entries for version 1.41.1 with bug fixes and version 2.0.1 with enhancements and bug fixes
  • Updates example configurations link from v1.41.0 to v1.41.1 in documentation
  • Adds new SSDLC compliance report file for v1.41.1 release

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
CHANGELOG.md Adds changelog entries for v1.41.1 and v2.0.1 releases with detailed feature, enhancement, and bug fix information
docs/index.md Updates example configurations link to reference v1.41.1 instead of v1.41.0
compliance/v1.41.1/ssdlc-compliance-1.41.1.md Adds new SSDLC compliance report for the v1.41.1 release

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

Copy link
Contributor

github-actions bot commented Oct 1, 2025

APIx bot: a message has been sent to Docs Slack channel

@oarbusi oarbusi changed the title chore: Updates CHANGELOG.md header and example link for v1.41.1 release chore: Updates CHANGELOG.md header, example link and SSDLC compliance report for v1.41.1 release Oct 1, 2025
@oarbusi
Copy link
Collaborator Author

oarbusi commented Oct 1, 2025

Cherry-picked b9c34fc to avoid example validation from failing because of no space left on device


## 1.41.1 (October 01, 2025)

BUG FIXES:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we shouldn't have 2.0.0 releases in the changelog for v1 releases

Copy link
Member

@lantoli lantoli Oct 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or maybe having CHANGELOG.md for the latest major version (2.x now), and having CHANGELOG-v1.md so they can evolve separately? and we don't need to decide how to merge 1.x and 2.x version changelogs together

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no strong opinion here. My idea was to keep both branches CHANGELOG updated with all versions. Open to alternatives

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's discuss offline

@oarbusi oarbusi merged commit f3727eb into master-v1 Oct 2, 2025
42 checks passed
@oarbusi oarbusi deleted the v1.41.1-changelog branch October 2, 2025 17:01
Copy link
Contributor

@jvincent-mongodb jvincent-mongodb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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.

4 participants