Changelog

circleci project create now lets you create a project from the CircleCI CLI. Run circleci project create -h for instructions.

The context restriction APIs have been promoted from experimental to generally available. Authorized users can now create, read, and delete project- and expression-based context restrictions via API. Security group context restrictions are not supported yet. Read the context API documentation.

CircleCI’s Visual Studio Code extension now lets customers trigger pipelines from VS Code based on local, unversioned configuration files. Users can choose to run a full pipeline, or select only the individual jobs and workflows they want to run by using checkboxes. This will shorten the feedback cycle and enable developers to iterate fast on their configuration, without having to commit their trial and error changes to the VCS.

It is now possible to monitor Gitlab and Github App projects through the VS Code extension. At this stage, these projects are not detected automatically by VS Code, but they can be selected manually through the settings page.

What’s New

CircleCI Personal and Project API access tokens have a new format. Previously, token values included a 40-character hex string. Newly created tokens will now include a CCIPAT or CCIPRJ prefix for personal access tokens or project access tokens, respectively:

What’s New

The CircleCI VS Code extension now allows monitoring multiple CircleCI projects in a single VS Code workspace. All CircleCI projects present in a workspace are now automatically detected and displayed in the Pipelines Panel when the workspace is loaded, whether it is a single-folder workspace or a multi-root workspace. Additional projects can be added through the settings page.

What’s New

You can now manage your config policies via the API. Previously, policies could only be managed via the CLI. This gives you options for how you create, validate, and retrieve decision logs for policies in CircleCI. For further information see the API reference docs.

What’s New

CircleCI’s CLI now includes an env subst command, which serves as a wrapper around the popular envsubst CLI tool. The command is used to substitute environment variables in a text string or file.

What’s New

Visual Studio Code users can now re-run CircleCI jobs with SSH, through either the integrated terminal, or a dedicated remote development window. You can automatically open an SSH connection within the terminal, or use a remote window to work on a CircleCI remote machine as if it was a VS Code workspace, which allows you to browse and view files easily, as well as take advantage of supported extensions.

What’s New

The CircleCI VS Code extension is now generally available. This extension provides an interface to visualize and manage CircleCI pipelines directly from VS Code. It also offers contextual help when creating, modifying, and editing CircleCI YAML configuration files.

What’s New

We have published the official CircleCI Visual Studio Code extension. This extension provides an interface to visualize and manage CircleCI pipelines directly from VS Code. It also offers contextual help when creating, modifying, and editing CircleCI YAML configuration files.

What’s New

The orb source, orb info, and orb/config validate CLI commands have been updated to work successfully with private orbs.

What’s New

CircleCI has just release 7 new Insights API endpoints to improve pipeline observability and tracking. You can now access even more insights features such as:

What’s New

You can now approve jobs with API v2. The new endpoint is POST /api/v2/workflow/:workflow-id/approve/:approval-request-id. The approval request id is the ID of a pending approval job, which will also be returned as an approval_request_id on approval jobs returned by the API. For more information see the API v2 docs.

What’s New

You can now show, create, delete and list Contexts via the CircleCI CLI. Run circleci update to get access to this new Context functionality.

What’s New

API v2 enables new functionality, such as triggering and retrieving pipelines and workflows via the API. Read more about it in our blog post.

What’s New

To unlist your published orbs from the registry, use the new circleci orb unlist CLI command. For details, refer to the help page. Unlisted orbs remain world-readable when referenced by name but will not appear in the search results of the orb registry. Unlisted orbs can be listed again using the circleci orb unlist <namespace/orb> false command.

What’s New

• Auto-cancel of redundant builds now supports workflows. Customers will need to turn on the Build Processing option under Advanced Settings in their project settings. See the istructions for Enabling Auto-Cancel for Workflows Triggered by pushed to GItHub or the API for details.