Skip to content

Use publish-1es-artifact instead of publish-artifact in archetype-tool-dotnet #8021

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Apr 4, 2024
Merged

Use publish-1es-artifact instead of publish-artifact in archetype-tool-dotnet #8021

merged 1 commit into from
Apr 4, 2024

Conversation

@scbedd
Copy link
Member

@scbedd scbedd commented Apr 4, 2024 •
edited
Loading

This has the knock on effect of fixing the proxy build.

  • produce-net-standalone-packs only used in archetype-tool-dotnet.yml
  • archetype-tool-dotnet is an extends on top of 1es-redirect.
  • Because it's only ever used in 1es context we're safe to swap the artifact publishing.

@scbedd scbedd requested a review from a team as a code owner April 4, 2024 00:51
@scbedd scbedd self-assigned this Apr 4, 2024
@scbedd scbedd merged commit f037d0e into main Apr 4, 2024
@scbedd scbedd deleted the fix-tool-archetype branch April 4, 2024 17:56
@maorleger maorleger mentioned this pull request Feb 4, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@benbp benbp benbp approved these changes

@weshaggard weshaggard weshaggard approved these changes

Assignees

@scbedd scbedd

Labels

None yet

Projects

Azure SDK EngSys 🍔🌭
Archived in project

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@scbedd @benbp @weshaggard