Closed cdaringe closed 2 years ago
hey @cdaringe sorry for not replying so long im currently moving into a new flat.
thx so much for your contribution,
i think we should also integrate releasing to Visual Studio Marketplace and openvsx.
i can add those tokens as variables to the secure context of the repository.
what do you think?
ah i think you already prepared and it need to add it as VSCE_PAT correct?
Greetings. No worries. I’m probably not going to come back to this for minimally weeks.
ya, submission to marketplace is done, just needs the secret added in your settings as VSCE_PAT. See https://code.visualstudio.com/api/working-with-extensions/publishing-extension#get-a-personal-access-token
hey @cdaringe
i finally got it merged.
there were some minor problems with tests, but i got it fixed :+1:
sorry for taking so long, i was in the hospital for some weeks.
Do you want to become Collaborator in the Project? You would get full repo permissions. I need some help to take care of it.
best regards Tristan
Hey @firsttris , ya im on board to help out
hope you’re recovering hastily. godspeed!
Problem
See #242
Solution
master
/trunk flowThe following was auto-published using my fork on the
main
branch, executing the same publish flow: https://marketplace.visualstudio.com/items?itemName=cdaringe.vscode-jest-runner-dummyI personally opt for semantic release, but that's a pretty big personal behavioral change, so i stuck with the highly functional and basic approach for this round.
You can still increment the version for minors and majors as seen fit, CI will just always release with a patch rev on top of your minor or major versions.