Skip to content

v0.9.0

Choose a tag to compare

@mzihlmann mzihlmann released this 31 Aug 12:19
· 109 commits to main since this release
7d75096

Update Notice

In this Release we activated these feature-flags:

⚠️ AZURE_AD_RESOURCE no longer has any effect while this flag is on. It only ever widened the audience, which is the opposite of what the flag is for.

FF_DOCKER_ACR_REGISTRY_SCOPED_TOKEN asks AAD for a token scoped to https://containerregistry.azure.net instead of https://management.azure.com/. The token is handed to whatever host came out of the image reference, as a Bearer header and as an access_token form field, so until now a host that got the token by mistake held one good for the whole subscription. It is now good for ACR and nothing else. No migration needed, the service principal or managed identity needs no extra role, the exchange the helper performs is the same one.

You can roll-back this change by overriding it in the environment ie.

job:
  variables:
    FF_DOCKER_ACR_REGISTRY_SCOPED_TOKEN: "0"

Please also notify us by filing a new issue.

What's Changed

Security

Maintenance

  • build(deps): bump step-security/harden-runner from 2.20.0 to 2.21.0: #5 #8
  • build(deps): bump github.com/google/go-containerregistry from 0.21.9 to 0.22.0: #10
  • build(deps): bump go from 1.26.5 to 1.26.7: #9
  • build(deps): bump github.com/docker/docker-credential-helpers from 0.9.8 to 0.9.9: #11

Fork Related

  • add a dependabot config: #4
  • add a funding config: #6
  • the nightly vulnerability scan swallows its exit code: #7

Refactorings

  • FF_DOCKER_ACR_AZIDENTITY=false acquire the token and exchange it through azidentity and azcontainerregistry instead of the retired go-autorest stack: #1