Repository navigation
ARSN-660: Bump the Arsenal epic to 8.6.1-bnaas.1 - #2737
Merged
anurag4DSB merged 1 commit intoOct 16, 2026
Merged
Conversation
Set the version on the BNaaS D1 epic to its first epic tag. After the merge, a GitHub pre-release 8.6.1-bnaas.1 on the epic starts the release workflow, which publishes under the npm dist-tag latest-8.6.1-bnaas. Vault, CloudServer and backbeat pin that tag next. Epic branch: epic/S3C-10971-bnaas-d1 Cut from: development/8.6 at 765bda8 on 2026-10-14 Last release on that line: 8.6.0 Changes since that release: 8.6.0...765bda8
fredmnl
approved these changes
Oct 14, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## epic/S3C-10971-bnaas-d1 #2737 +/- ##
===========================================================
- Coverage 75.39% 75.38% -0.02%
===========================================================
Files 226 226
Lines 18633 18633
Branches 3895 3895
===========================================================
- Hits 14048 14046 -2
- Misses 4580 4582 +2
Partials 5 5 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
nicolas2bert
approved these changes
Oct 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Intent: why does this change exist?
BNaaS D1 needs its own Arsenal tag for Vault, CloudServer and backbeat to pin, without moving the 8.6 line. This is task 3, row 3.1 in the Tickets tab of the BNaaS D1 tech spec.
System impact: what's affected, including downstream?
Only the epic branch. After the merge, a GitHub pre-release
8.6.1-bnaas.1on the epic starts the release workflow, which publishes under the npm dist-taglatest-8.6.1-bnaas, solatest-8.6stays on 8.6.0. The manual workflow run refuses epic branches, so the GitHub release is the only path, and it must be marked as a pre-release to stay off arsenal's latest release.Preserved behavior: what explicitly stays the same?
No code changes. The commit touches only
version, like every past release commit.Intended change: what's different after this PR?
The epic's
package.jsonsays8.6.1-bnaas.1. The commit message records where the epic comes from: the cut sha, the last release on the line and the compare link.Verification: how do we know this worked, or how would we know if it didn't?
The usual lint and test CI runs on this PR. After the release,
npm view @scality/arsenal dist-tagsmust showlatest-8.6.1-bnaas: 8.6.1-bnaas.1, withlatest-8.6still on 8.6.0.