Trigger first release to open-vsx.org: take 2#2
Conversation
75c4f3d to
08818f6
Compare
09b3104 to
28bac07
Compare
08818f6 to
7da8139
Compare
7da8139 to
11e8d7d
Compare
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
14b0e44 to
d7a4669
Compare
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
121aa60 to
6bc8583
Compare
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
da7e332 to
90ec1bd
Compare
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
90ec1bd to
8270e1a
Compare
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
8270e1a to
10cc3b0
Compare
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
10cc3b0 to
5b984d5
Compare
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
5b984d5 to
61d86a7
Compare
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
6828f44 to
e8eccfc
Compare
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.2.0 with changes since v0.0.0
|
The license check can be triggered locally: yarn license:check For automatic opening of IP tickets for suspicious depedencies, set an Eclipse Foundation gitlab token as environment variable "DASH_TOKEN" and run the alternate pacakge.json script. e.g.: export DASH_TOKEN="<your token>" yarn license:check:reviewAdd 3PP license check as part of PR CI Closes eclipse-cdt-cloud#189 Signed-off-by: Marc Dumais <marc.dumais@ericsson.com>
- Renamed the build workflow to ci-cd and made modifications:
- added a publish job, that publishes the .vsix extension to openvsx.org,
triggered only when a release tag (v<something>) is pushed to the repo.
- merged the build and ui tests jobs. They were redundent, both building
the project
- removed yarn package caching: practically it helped very little, cutting
only ~5% vs the time it takes to install the dependencies without
~(25s vs 26s) in the best case (cache hit). With a cache miss (run with
modified yarn.lock), we had a 100+% penalty, if we count the overhead
of the cache being saved to GitHub infrastructure.
- created a "release" workflow that uses "pipe-cd/actions-gh-release" to
to create a release tag and corresponding GitHub release, when a change
is detected in root file "RELEASE".
- TL;DR: this is how a release is triggered, by adding the tag value
reflecting release version, to RELEASE file as part of a PR. The
action will add tentative release notes to the PR that can be edited
as needed. Upon merging the PR, a release tag will be created in the
repo, which will trigger the publish job, that will eventually result
in the new version of the extension being deployed to openvsx.org
- it looks like the RELEASE file must exist before its first use in a PR,
so created one with no active content.
- added "doc/Publishing.md" to briefly document how to go about creating new
releases / publish new releases to openvsx.org
- renamed public-facing name (displayName) of the extension to "Trace Viewer
for VSCode", to better reflect its nature
- changed public-facing mentions of "vscode" to the canonical "VSCode"
- changed extension's publisher, to align with the configuration of the CDT
Cloud OpenVSX publisher user: "eclipse-cdt". See:
https://www.open-vsx.org/namespace/eclipse-cdt
- other misc updates to the extension's package.json: added/massaged important
fields
(https://www.open-vsx.org/namespace/eclipse-cdt).
- kept developer-specific information in repo's root README.md but moved
generic information, useful to users of the extension, to extension's
README (which becomes the information page for the extension when published
or installed).
- Added an icon for the extension. Though probably not the best ever, re-used
the one from repo "theia-trace-extension"
Closes eclipse-cdt-cloud#69
Signed-off-by: Marc Dumais <marc.dumais@ericsson.com>
Signed-off-by: Marc Dumais <marc.dumais@ericsson.com>
The wrong license had been added by mistake- use the correct one: MIT Signed-off-by: Marc Dumais <marc.dumais@ericsson.com>
Signed-off-by: Marc Dumais <marc.dumais@ericsson.com> try a few options for generation of release notes Signed-off-by: Marc Dumais <marc.dumais@ericsson.com> try more options for generation of release notes Signed-off-by: Marc Dumais <marc.dumais@ericsson.com> try even more options Signed-off-by: Marc Dumais <marc.dumais@ericsson.com> try even more options... Signed-off-by: Marc Dumais <marc.dumais@ericsson.com> try even more options... try not showing committer Signed-off-by: Marc Dumais <marc.dumais@ericsson.com>
1ed3cb0 to
c9abf6e
Compare
28bac07 to
52d408f
Compare
Signed-off-by: Marc Dumais <marc.dumais@ericsson.com>
c9abf6e to
e96f3a9
Compare
52d408f to
15e3e9f
Compare
No description provided.