Skip to content

Auto-trigger release pipeline on main merge and check npm versions before publish#3334

Closed
msyyc wants to merge 2 commits intomainfrom
publish/release-2026-02-05
Closed

Auto-trigger release pipeline on main merge and check npm versions before publish#3334
msyyc wants to merge 2 commits intomainfrom
publish/release-2026-02-05

Conversation

@msyyc
Copy link
Member

@msyyc msyyc commented Feb 6, 2026

Changes

  • Auto-trigger release pipeline: The release pipeline now triggers automatically when changes are merged to the \main\ branch, removing the need for manual triggers.
  • Pre-publish npm version check: Added a step that runs early in the pipeline (before installing dependencies or running tests) to verify that the current package versions are not already published to npm. This avoids wasting time on builds and tests when the versions are already released.
    • Checks @azure-tools/typespec-python\
    • Checks @autorest/python\
  • Updated README: Reflects the new automatic release behavior.

@msyyc msyyc force-pushed the publish/release-2026-02-05 branch from eefd4f7 to 8183ac3 Compare February 6, 2026 04:56
@msyyc msyyc closed this Feb 6, 2026
@msyyc msyyc deleted the publish/release-2026-02-05 branch February 6, 2026 04:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant