Skip to content

Releases

2.5.2

Choose a tag to compare

@tomverin tomverin released this 10 Nov 09:50
Immutable release. Only release title and notes can be modified.
e2032bd

What's Changed

Bug Fixes

  • PREQ-10194: Bump config-npm cache pin to gh-action_cache v1.7.5 by @tomverin in #374

    config-npm now uses gh-action_cache v1.7.5. Merge-queue refs (refs/heads/gh-readonly-queue/*) no longer run the npm S3 cache save. That save cannot succeed, and the post-step could hang until the job timeout after s3:PutObject AccessDenied. Restore still runs, including the default-branch fallback. The bump also picks up the v1.7.4 StepSecurity pin of runs-on/cache.

    Workflows on SonarSource/ci-github-actions/config-npm@v2 pick this up with this v2 branch update. Callers pinned to a commit SHA stay on v1.7.3 until they bump.


Full Changelog: 2.5.1...2.5.2

1.8.10

Choose a tag to compare

@tomverin tomverin released this 10 Nov 10:36
Immutable release. Only release title and notes can be modified.
0bcfefc

What's Changed

Bug Fixes

  • PREQ-10194: Backport config-npm cache pin to gh-action_cache v1.7.5 by @tomverin in #375

    config-npm on the v1 branch now uses gh-action_cache v1.7.5. Merge-queue refs (refs/heads/gh-readonly-queue/*) no longer run the npm S3 cache save. That save cannot succeed, and the post-step could hang until the job timeout after s3:PutObject AccessDenied. Restore still runs, including the default-branch fallback. The bump also picks up the v1.7.3 Cognito retries and the v1.7.4 StepSecurity pin. path, key, and restore-keys are unchanged.

    Workflows on SonarSource/ci-github-actions/config-npm@v1 pick this up with this v1 branch update. This is the same pin already released on v2 in 2.5.2.


Full Changelog: 1.8.9...1.8.10

2.5.1

Choose a tag to compare

@hedinasr hedinasr released this 27 Oct 13:37
Immutable release. Only release title and notes can be modified.

Bug Fixes

  • Fixed the "Clean up local action symlinks" step failing on Windows runners with rm: cannot remove '.actions/get-build-number': Is a directory. Git Bash copies directories for ln -s, so the cleanup now uses rm -rf, which removes a copy or a symlink but never the symlink target. Affects config-npm, config-poetry, config-uv, build-npm, build-poetry and build-yarn (#371, BUILD-13259)

Full Changelog: 2.5.0...2.5.1

2.5.0

Choose a tag to compare

@hedinasr hedinasr released this 27 Oct 09:31
Immutable release. Only release title and notes can be modified.

What's Changed

New Features

  • BUILD-13251: Add the config-bun action, which points Bun at the Repox registry selected by repox-url (SaaS on GitHub-hosted runners, production Edge on self-hosted runners), exports BUN_CONFIG_REGISTRY, BUN_CONFIG_TOKEN, ARTIFACTORY_USERNAME and ARTIFACTORY_ACCESS_TOKEN from the matching Vault reader, and caches ~/.bun/install/cache, by @hedinasr in #369

Dependency Updates

Package Update Change
Node.js (repository mise tooling) patch 24.15.0 → 24.22.1 (#370)

config-bun does not modify bun.lock. Bun downloads locked packages from the absolute tarball URLs written in bun.lock, so commit a lockfile resolved through the same Repox as repox-url. See the config-bun README section.

permissions:
  id-token: write
steps:
  - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
  - uses: step-security/mise-action@a225bbd7c202ddf57dd76dff22bb7992f6314173 # v5.1.2
  - uses: SonarSource/ci-github-actions/config-bun@v2
  - run: bun ci

Full Changelog: 2.4.2...2.5.0

2.4.2

Choose a tag to compare

@hedinasr hedinasr released this 26 Oct 08:29
Immutable release. Only release title and notes can be modified.
962ef7d

What's Changed

Bug Fixes

  • PREQ-9667: Update config-uv, config-poetry, config-npm, build-npm, build-yarn, build-poetry, promote and update-release-channel to mise 2026.10.17, which drops trust in the compromised eMudhra certificates, by @roxanachiric-sonar in #366

Internal & Chores

  • PREQ-9667: Update the mise pin to 2026.10.17 in the test-build-number, test-shell-scripts and test-update-release-channel workflows by @roxanachiric-sonar in #366

New Contributors


Callers of the v2 branch pick this up with no workflow edit. SHA-pinned callers stay on mise 2026.10.6 until they bump.

Full Changelog: 2.4.1...2.4.2

2.4.1

Choose a tag to compare

@tomverin tomverin released this 23 Oct 14:01
Immutable release. Only release title and notes can be modified.
53ae810

What's Changed

Improvements

  • BUILD-13184: Pin published composite actions from jdx/mise-action to step-security/mise-action v5.1.2 (a225bbd7c202ddf57dd76dff22bb7992f6314173) and from re-actors/alls-green to step-security/alls-green v1.3.0 (42a30a1f2469c81cb95ae89a722da4c1c4fcc240) by @tomverin in #364

Documentation

  • Point README mise examples at step-security/mise-action by @tomverin in #364

config-gradle stays on gradle/actions/setup-gradle v6. step-security/gradle-actions publishes setup-gradle only on major v5, so that pin is unchanged.

Callers of the v2 branch pick this up with no workflow edit. SHA-pinned callers stay on the previous pin until they bump.

Full Changelog: 2.4.0...2.4.1

2.4.0

Choose a tag to compare

@bwalsh434 bwalsh434 released this 22 Oct 20:41
Immutable release. Only release title and notes can be modified.

What's Changed

New Features

  • BUILD-12980: Resolve dependencies through production JFrog Edge by default on self-hosted runners. GitHub-hosted runners continue to use SaaS Repox, and explicit repox-url inputs override the default. Deployment, publication, build info and promotion continue to use SaaS. By @hedinasr in #359

Improvements

  • BUILD-12911: Obtain production Edge reader credentials through production Vault. Development Edge overrides continue to use development Vault and their matching reader credentials. By @bwalsh434 in #357
  • Update shared GitHub Actions dependencies by @renovate[bot] in #340
  • Update jdx/mise-action to v5 by @renovate[bot] in #356

Bug Fixes

  • BUILD-12998: Fix build-number reference authorization for PR merge commits by anchoring coordination references to the repository’s default-branch HEAD. contents: write remains sufficient. By @guillaume-dequenne in #360

Documentation

  • Document runner-based dependency endpoints, explicit overrides, network requirements and consumer migration prerequisites in the README, included in #359

New Contributors


Full Changelog: 2.3.0...2.4.0

2.3.0

Choose a tag to compare

@tomverin tomverin released this 05 Oct 12:13
Immutable release. Only release title and notes can be modified.
6246338

What's Changed

New Features

  • build-maven input skip-build (default false): analyze an existing target/ tree without compiling, testing, or deploying. Requires deploy: false and an enabled Sonar analysis. The step fails if target/classes is missing, or if analysis is disabled so the job would do nothing. README includes a producer/consumer example (upload **/target, restore it, then scan). PREQ-8698 by @mary-georgiou in #348

Full Changelog: 2.2.0...2.3.0

2.2.0

Choose a tag to compare

@hedinasr hedinasr released this 01 Oct 14:41
Immutable release. Only release title and notes can be modified.
2.2.0

What's Changed

New Features

  • New config-nuget action: reads a Repox reader token from Vault and exports it as ARTIFACTORY_USER/ARTIFACTORY_PASSWORD for the packageSourceCredentials of NuGet configuration files. With repox-url: https://repox-internal.dev.sonar.build, the token is issued by the JFrog Edge and the https://repox.jfrog.io/artifactory/ package sources of the listed nuget-config-files are rewritten to the Edge, so committed files can keep SaaS Repox for local builds. Runs on Linux and Windows runners (#354, BUILD-12160)

Documentation

  • New config-nuget README section, covering the in-place rewrite of the listed files, repeat calls in the same job, and NuGet package caching left to the calling workflow (#354, BUILD-12160)

Internal & Chores

  • ShellSpec coverage and SonarCloud analysis for config-nuget (#354, BUILD-12160)

Full Changelog: 2.1.0...2.2.0

2.1.0

Choose a tag to compare

@hedinasr hedinasr released this 01 Oct 09:13
Immutable release. Only release title and notes can be modified.

What's Changed

New Features

  • Resolve dependencies through the JFrog Edge by setting repox-url: https://repox-internal.dev.sonar.build on the config-* and build-* actions. With the Edge, the resolve token is issued by the Edge through development/artifactory-edge-dev on https://vault.dev.sonar.build. The default stays https://repox.jfrog.io, so existing workflows are unchanged. Deployment, publication, build info and promotion always use https://repox.jfrog.io (#350, BUILD-12158)

Improvements

  • check-sca: the "grant access" deep link on SCA-check failures now prefills the Port manage_vault_policy org-first picker (github_organization and github_repository) (#352, BUILD-12598)

Documentation

  • New "Resolving through the JFrog Edge" README section (#350, BUILD-12158)

promote no longer accepts repox-url: promotion always targets https://repox.jfrog.io. No known consumer sets it; workflows that still pass it get an "Unexpected input" warning and promote on SaaS Repox as before.

Full Changelog: 2.0.1...2.1.0