update-api-console-components

Automating the api-console npm release workflow handles component version updates, GPG signing, npm publishing, and branch management. It requires a clean working directory, git with GPG signing configured, and npm access to ensure compliant releases.

Synchronizing the anypoint-api-console wrapper across repos requires propagating updates after publishing api-console v6. This Skill automates wrapper synchronization by managing branch naming and updating wrapper work items across repositories.

Yes, GPG signing is required to publish api-console v6 releases. You need git configured with GPG signing, access to npm, and knowledge of targeted components and wrapper work items to ensure compliant, auditable releases.

Before starting an api-console release, you need a clean working directory, access to npm, git with GPG signing configured, and knowledge of targeted components and wrapper work items to ensure a repeatable, auditable release flow.

Branch management during an api-console release enforces specific branch naming conventions and calculates versions automatically. This ensures a repeatable, auditable flow when updating component dependencies and propagating wrapper updates across repos.

A clean working directory is required for the api-console release workflow to prevent conflicts during component version updates, GPG signing, and npm publishing. It ensures the automated release process maintains consistency and auditability.