Skip to content

Move 1ES pipeline to correct dir#1939

Closed
bosesuneha wants to merge 1 commit intoAzure:mainfrom
bosesuneha:move-1es-pipeline
Closed

Move 1ES pipeline to correct dir#1939
bosesuneha wants to merge 1 commit intoAzure:mainfrom
bosesuneha:move-1es-pipeline

Conversation

@bosesuneha
Copy link
Copy Markdown
Member

@bosesuneha bosesuneha commented Feb 27, 2026

The 1es pipeline is an azure pipeline, so having it in .github/workflows folder results in error since github writes to read it as a github workflow. Moving it to a separate directory .azuredevops.

Note: Before merging this we need to verify if the path of the pipeline is changed in the actual ado pipeline

@Tatsinnit
Copy link
Copy Markdown
Member

💡 This will break the whole 1ES setting, so please do-not merge this we need to align this Ater the release and when we have the whole transition window.

@Tatsinnit Tatsinnit added the do-not-merge Not ready for merge yet (but ready for testing and review) label Feb 27, 2026
Copy link
Copy Markdown
Member

@Tatsinnit Tatsinnit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Leaving a note here as well, could we please hold off on merging this for now? This change will require us to recreate the ADO pipeline, so it would be good to align both pieces of work closely once we’re ready to move forward.

Given we have a few tight releases planned over the coming days, I’d suggest we avoid merging this until things settle a bit.

Thanks so much, gentle cc: @bosesuneha

@bosesuneha
Copy link
Copy Markdown
Member Author

Yes, this need not be merged now. We can revisit after the CA preview release.

@Tatsinnit
Copy link
Copy Markdown
Member

Yes, this need not be merged now. We can revisit after the CA preview release.

Sounds Great, can we please move PR to Draft for now, 👍 Thank you.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

publishVersion defaults to 0.0.1, but package.json currently declares version 1.6.15. For a publishing/release pipeline, this default can easily create incorrect tags/releases; consider making the parameter required (no default) and/or validating it against package.json before creating the GitHub release/tag.

Suggested change

Copilot uses AI. Check for mistakes.
Comment on lines 192 to 196
Copy link

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The token is defined as a normal runtime parameter and then passed into the publish step. Azure DevOps runtime parameters are not secret, so this PAT can be exposed in run metadata/logs; use a secret pipeline variable/variable group (or a service connection) instead, and avoid printing any part of the token in logs.

Suggested change
npx vsce publish --pat "$TOKEN" --packagePath "$VSIX_PATH"
env:
# TOKEN should be defined as a secret variable (e.g., in the pipeline or a variable group)
TOKEN: $(MARKETPLACE_PAT)

Copilot uses AI. Check for mistakes.
Comment on lines 2 to 5
Copy link

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

trigger: none disables CI triggers, but PR validation triggers are controlled separately. If this pipeline is intended to run only manually, add pr: none as well to avoid accidental runs on pull requests (especially since it includes signing/publishing steps).

Suggested change
pr: none
# The `resources` specify the location and version of the 1ES PT.
resources:

Copilot uses AI. Check for mistakes.
@bosesuneha bosesuneha marked this pull request as draft February 27, 2026 21:22
@bosesuneha bosesuneha closed this Mar 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge Not ready for merge yet (but ready for testing and review)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants