Skip to content
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.

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

fix: change package scope to @progress #26

Merged
merged 5 commits into from
Jun 2, 2022
Merged

fix: change package scope to @progress #26

merged 5 commits into from
Jun 2, 2022

Conversation

tsvetomir
Copy link
Member

@tsvetomir tsvetomir commented Jun 2, 2022

Cleaning up the @telerik scope for internal usage.

Will publish this as @progress/semantic-prerelease v3.0.0

@tsvetomir tsvetomir requested a review from kspeyanski June 2, 2022 10:33
Copy link
Contributor

@kspeyanski kspeyanski left a comment

Choose a reason for hiding this comment

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

Should we use secrets.NPM_TOKEN instead of NPM_TOKEN_TELERIK in cd.yml?

I'm suspicious that both tokens would have access to the @progress scope, but I may be wrong.

@tsvetomir
Copy link
Member Author

Good catch, they're separate.

@tsvetomir tsvetomir marked this pull request as ready for review June 2, 2022 13:33
@tsvetomir
Copy link
Member Author

Published a 3.0.0 version manually so semantic release can hopefully take off from there 🤞🏽

The package is still not visible in the registry, but is installable. I f-ed up a bit by un-publishing the only version of the new version and it's now in a 24-hour cool-down period during which it doesn't officially exist.

@tsvetomir tsvetomir merged commit 0844262 into develop Jun 2, 2022
@tsvetomir tsvetomir deleted the fix-scope branch June 2, 2022 13:36
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.

2 participants