-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Publish to VS Marketplace #40
Conversation
cf73e1e
to
b0127ef
Compare
Modify the GitHub Actions workflow by adding: - gitversion job - setup-node step - version step - cache step - publish step
b0127ef
to
c31053d
Compare
nice! |
7fc923d
to
529f8ed
Compare
529f8ed
to
1fbdb3f
Compare
@wooorm, I need to add a Personal Access Token or have one of you create one and add it as the GitHub secret |
75654d4
to
df913db
Compare
It looks like an azure org is needed for that? So that is a different one from unifiedjs on the marketplace? And I need to set that up? |
Yes, I've created unifiedjs on Azure DevOps and invited you, @ChristianMurphy and @JounQin to it.
Pretty silly, but yes. 🙄
No, I have. |
I think you should receive an e-mail invitation you need to accept, @wooorm. |
Thank you so much for the code review, @joebowbeer! It still fails, however:
Ideas? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See suggested change.
Co-authored-by: Joe Bowbeer <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current version might be as good as it gets without editing package.json.
But this is one more thing to try.
However, I'm rethinking my assumption that this is possible without editing package.json.
The published package includes package.json. Having a package published as scoped claim in its package.json that it is unscoped may be troublesome.
When I accept, I get that 401 from #40 (comment). |
Co-authored-by: Joe Bowbeer <[email protected]>
It's really stupid, but as explained in this Stack Overflow answer, please try to open unifiedjs in an incognito Window or a separate browser and sign in with the invited e-mail address.
Yeah, I get it. I just can't yet accept that Azure DevOps is so useless that it's impossible to invite users to the organization. Let's please give this another go. |
Thanks, @joebowbeer! It still fails, unfortunately:
Yeah, that makes sense. Sad that unscoped packages aren't supported by GPR, though. |
I tried again. Private window. And different browser. To no avail. I also got this one, weirdly. But I solved that by adding a phone number: It’s unrelated to these codes, right? #28 (comment) Could you maybe remove me from the org, and add me again? (i.e., the age old: have you tried turning it off and on again 😅) |
Yes, those codes were used to have you invited to the VSCE Marketplace.
Sure, I've just removed and added you back to the organization. I hope that helps! 🤞🏼 |
It didn’t 😭 |
Meanwhile, to get this unblocked, I’m guessing that you can create such a token and I can add it. Could you DM/email me one? |
😭
Sure, I'll pop you an e-mail. |
@wooorm Did you add the VSCE_TOKEN to |
I just added a |
Tweaks the GitHub Actions workflow to publish the extension to the VS Marketplace.
Resolves #38.