chore(deps): SP-262 consolidate docs dependencies - #26
Open
Sourceless wants to merge 1 commit into
Open
Conversation
Sourceless
marked this pull request as ready for review
August 28, 2026 08:59
This was referenced Aug 28, 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.
Verification
RBENV_VERSION=3.2.2 bundle installindocs/bundle exec jekyll build --tracemake tooling && make check— 3 tests, 0 failures/errors/skips; SpotBugs and Spotless greengit diff --checkWhat / why
Consolidates the two scoped Dependabot docs lockfile updates for SP-262:
concurrent-ruby1.3.8 andjson2.21.2. Supersedes #24 and #25 after merge-stage disposition.Impact / risk
Docs lockfile only. No application, workflow, infrastructure, or permissions changes. The repository has no PR check; SP-262 Jira comment 56639 provides the ticket-only bounded exception, backed by the clean local build above.
Dev-deploy decision
Not applicable: this is a docs lockfile-only change with no deployable dev target. Pages publication remains a post-merge observation.
Scope escalation
None. No hardened path was deleted or replaced.