Changelog

Changes:

• Added support for missing progressive canary step types. These include:
  • Experiment
  • Set canary scale
  • Set header route
  • Set mirror route
• Fixed a bug where a CANCEL RELEASE command canceled the wrong release

Deprecation Note:

• After April 1, 2024 all Release Agent versions prior to 1.0.0 will no longer be supported. Please update your agent before then to continue seeing your releases in the CircleCI UI.
• For update instructions, review the Release Agent documentation.

An “unauthorized” error message is shown when a user does not have access to contexts required to run the job.

Keep reading

Changes:

• The circleci.com/project-id annotation is now required in order for components and releases to be tracked and displayed in the UI
• Removed the ROLLBACK type releases in favor of the true underlying type (PROGRESSIVE or DEPLOYMENT) and have added a RERELEASE tag
• Improved clarification notes on RESTORE_VERSION command output
• Avoid retrying calls to the cloud in case of 400 and 401 status code responses

Deprecation Note:

• After April 1, 2024 all Release Agent versions prior to 1.0.0 will no longer be supported. Please update your agent before then to continue seeing your releases in the CircleCI UI.
• For update instructions, review the Release Agent documentation.

Runner Release

• Fix bug causing the kube-api server to sometimes prematurely terminate task pods for containerized jobs.
• Improve Task Lifecycle step with dynamic Kubernetes pod lifecycle status for containerized jobs. Providing more detailed information on each step in the lifeycle, making it easier to debug issues if they arise.

Experimental Contexts Restriction API change:

Keep reading

We have updated our current onboarding survey by reducing the number of questions and introducing dynamic capabilities that tailor the survey based on the user’s responses.

Users can now name their CircleCI organization when using CircleCI’s GitHub App or GitLab integration.

The CircleCI UI now uses the language “Needs Approval” instead of “On Hold” to denote that an approval job is pending approval.

Keep reading

We have resolved a bug which prevented users from creating GitHub App triggers if they had previously deleted all of their triggers.

For projects that integrate with CircleCI’s GitHub App, you can now specify a custom configuration source when creating a GitHub App trigger.

This enables you to use modular configuration files within the same project (ie. a build-and-test.yml and a deploy.yml that have different definitions).