Conversation
This was referenced Sep 12, 2026
lipkau
added a commit
that referenced
this pull request
Sep 15, 2026
### Description - Reuse one `update-<Module>` branch and pull request per module, serialize updates per module, and reject stale or unrelated release tags. - Pin every third-party action to an immutable commit and scope Pages permissions to the build and deploy jobs that need them. - Move the AtlassianPS.Configuration submodule to the latest stable release, v0.2.10, and remove its obsolete documentation-only exception. ### Motivation and Context This converges website release updates instead of accumulating version-specific pull requests. It also closes the current Configuration documentation gap and hardens the affected workflows without adding another automation layer. Refs AtlassianPS/AtlassianPS#13 (WP2). This does not close the umbrella issue. After maintainer review and merge, #59 and #63 can be closed as superseded. #53 remains the separate `actions/checkout` v7 upgrade and should be refreshed against the pinned workflow after this change lands. ### Types of changes - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ### Validation - `actionlint -color` (actionlint 1.7.12): passed. - Immutable action-reference assertion across `.github/workflows/*.yml`: passed. - Rolling-branch and exact-tag/stale-release guard assertions: passed; v0.2.10 was accepted and v0.2.9 after v0.2.10 was rejected. - `bash .github/scripts/check-module-submodules.sh`: passed for Configuration v0.2.10, ConfluencePS v2.5.2, JiraAgilePS v0.1.1, and JiraPS v2.16. - `env BUNDLE_PATH=.tmp/vendor/bundle BUNDLE_APP_CONFIG=.tmp/bundle-config JEKYLL_ENV=production bundle exec jekyll build --baseurl ""`: passed; only the existing Bootstrap Sass deprecation warning was emitted. - `git diff --check`: passed. - Independent final diff review: no remaining findings. No dependency updater, release workflow, tag, package, or deployment was dispatched. ### Checklist - [x] My code follows the code style of this project. - [ ] Pester tests are not applicable to this workflow/documentation repository. - [x] I have updated the documentation accordingly.
Member
Author
|
Superseded by #64. Master now points AtlassianPS.Configuration at v0.2.10, and future module releases use one rolling update branch per module. |
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
1 participant
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.
Automated update of AtlassianPS.Configuration submodule to v0.2.9.
Triggered by: repository_dispatch