-
Notifications
You must be signed in to change notification settings - Fork 1
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: SonarSource/ci-github-actions
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 1.3.27
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: SonarSource/ci-github-actions
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 1.3.28
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 6 commits
- 48 files changed
- 3 contributors
Commits on Mar 13, 2026
-
BUILD-10586 Fix inconsistencies between actions inputs, outputs and b…
…ehaviors - Add `deploy` input to build-npm, build-yarn, build-poetry (consistent with build-maven/build-gradle) - Enable deployment on long-lived feature branches (feature/long/*) for npm/yarn/poetry - Add `disable-caching` input to build-npm, build-yarn, config-npm; deprecate `cache-npm`/`cache-yarn` - Add `should_scan()` to build-gradle to filter SonarQube analysis by branch type - Add CONFIG_NPM_COMPLETED idempotency guard to config-npm (consistent with config-gradle/config-maven) - Condition Artifactory deploy token vault secret on deploy being enabled - Align shadow scan warning to GitHub Actions ::warning stderr format across all actions - Align run-shadow-scans description and sh header documentation across all build actions - Fix artifactory-deploy-repo description in build-npm (private-qa was incorrectly named public-qa) - Update README: deployment strategy table, input tables, remove resolved known bugs and TODOs - Code style: consolidate parameter validation, fix readonly declarations, align sh header labels Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Configuration menu - View commit details
-
Copy full SHA for 9014b55 - Browse repository at this point
Copy the full SHA 9014b55View commit details
Commits on Mar 23, 2026
-
BUILD-10591 Leverage JFrog CLI summary in build-npm, build-yarn, buil…
…d-poetry and promote Generate the JFrog CLI job summary explicitly rather than relying on the setup-jfrog-cli post-step, which fails and conflicts with the CLI. **JFrog CLI configuration fixes (build-npm, build-yarn, build-poetry, config-npm, promote)**: - Add --url flag to 'jf config add repox' with the JFrog Platform URL (base URL without '/artifactory') - Add 'jf config use repox' (or 'deploy' for maven) after 'jf config add' to explicitly activate the server configuration - In promote.sh and build scripts, suppress 'jf config remove repox' output (redirect to /dev/null) - Make ARTIFACTORY_URL required (via :?) in promote.sh **JFrog CLI command summary (all build actions + promote)**: - Set JFROG_CLI_COMMAND_SUMMARY_OUTPUT_DIR in build step env so JFrog CLI writes command summary data during execution - build-maven/deploy-artifacts.sh: also set JFROG_CLI_COMMAND_SUMMARY_OUTPUT_DIR in the Artifacts upload step **Generate workflow summary (all build actions)**: - Merge JFrog CLI summary generation into 'Generate workflow summary' step (remove the separate 'Generate JFrog CLI summary' step) - Add JFrog summary support to build-maven (when mixed-privacy=true, using 'jf config use deploy') and build-gradle - Rework summary format: extract Published Modules from JFrog markdown.md (bold module names and multi-line <pre> file tree blocks) into a collapsible <details> block - Change build URL link text from 'Browse artifacts in Artifactory' to 'Browse build `name:number` in Artifactory' **promote/action.yml**: - Add repox-url and repox-artifactory-url inputs (forwarded from callers) - Add ARTIFACTORY_URL env var to the Promote artifacts step **Other**: - Upgrade renovatebot/pre-commit-hooks to 43.76.3 in .pre-commit-config.yaml - Fix trailing spaces in deprecation warning messages (cache/action.yml, config-npm/action.yml, build-npm/action.yml, build-yarn/action.yml) - Minor doc fix in build-maven/build.sh and promote/promote.sh - Update spec tests to match new command signatures and line counts (100% coverage) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Configuration menu - View commit details
-
Copy full SHA for 44a1e8f - Browse repository at this point
Copy the full SHA 44a1e8fView commit details -
BUILD-10591 Extract JFrog CLI summary into shared/generate-jfrog-summ…
…ary.sh Deduplicate the 16-line JFrog CLI summary extraction block that was copy-pasted verbatim across build-npm, build-yarn, build-poetry, and build-maven action.yml files. - Add shared/generate-jfrog-summary.sh accepting <jf-server-id> as $1 - Replace each inline block with "$ACTION_PATH_SHARED/generate-jfrog-summary.sh" repox|deploy - Add spec/shared_generate-jfrog-summary_spec.sh with 9 test cases - Fix config-npm spec: --url strips /artifactory suffix (${ARTIFACTORY_URL%/artifactory*}) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>Configuration menu - View commit details
-
Copy full SHA for 80f82d5 - Browse repository at this point
Copy the full SHA 80f82d5View commit details
Commits on Mar 25, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 43f69d1 - Browse repository at this point
Copy the full SHA 43f69d1View commit details -
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Configuration menu - View commit details
-
Copy full SHA for 77ac9f9 - Browse repository at this point
Copy the full SHA 77ac9f9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9be4971 - Browse repository at this point
Copy the full SHA 9be4971View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 1.3.27...1.3.28