chore(ci): remove SonarCloud and contractor-specific staging deploy trigger#53
Merged
gkostkowski merged 3 commits intoJul 15, 2026
Merged
Conversation
…rigger Drop the SonarCloud scan job along with sonar-project.properties, and remove the trigger-staging-deploy job that referenced the contractor ops repo. Bump version to 1.1.0-rc.6 and update the CHANGELOG.
There was a problem hiding this comment.
Pull request overview
This PR cleans up CI/CD configuration by removing unused SonarCloud wiring and a contractor-specific staging deploy trigger, and bumps the project version to align with the release-candidate changelog entry.
Changes:
- Remove SonarCloud scan configuration (CI job +
sonar-project.properties). - Remove the contractor-specific staging deploy workflow dispatch from CI.
- Bump version to
1.1.0-rc.6and add a matchingCHANGELOG.mdentry.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
src/VERSION |
Bumps the release-candidate version to 1.1.0-rc.6. |
sonar-project.properties |
Deletes unused SonarCloud configuration for this fork. |
CHANGELOG.md |
Adds a 1.1.0-rc.6 entry (needs minor adjustments per comments). |
.github/workflows/ci.yaml |
Removes SonarCloud scan steps and the staging deploy trigger job (needs header comment update per comments). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Summary
ci.yamland deletesonar-project.properties.trigger-staging-deployjob, which dispatched a deploy workflow on a contractor-specific ops repository.1.1.0-rc.6and add the correspondingCHANGELOG.mdentry.Notes for the upstream repo
These CI changes have no effective impact on the upstream repository: SonarCloud was never actually configured for this fork (no
SONAR_TOKENsecret was ever provisioned), so the SonarCloud job was effectively a no-op. Removing it simply cleans up dead configuration rather than changing any real behavior. Likewise, the staging-deploy trigger targeted a contractor-owned ops repo that is not part of the upstream deployment flow, so its removal does not affect upstream pipelines.Test plan
make test-unitpasses locallyReferences