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 Dependabot/GitHub actions/actions/upload artifact 4 #1065

Conversation

Alidra
Copy link
Member

@Alidra Alidra commented Mar 6, 2024

Upgrading actions/upload-artifact@v2 to v4 breaks the generation the Vscode extension in the pipeline because this new version doesn't allow the artifacts exported by the pipeline to have the same name (previous was to replace existing artifacts).

To fix this, a separate job is dedicated to the generation of the Vscode extension independently from OCaml version which avoids multiple generations.

Besides, the nodejs version has been upgrated to newest version (up to 20)

@fblanqui fblanqui merged commit cf607ec into Deducteam:dependabot/github_actions/actions/upload-artifact-4 Mar 6, 2024
10 checks passed
Alidra added a commit that referenced this pull request Mar 6, 2024
* Bump actions/upload-artifact from 2 to 4

Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 2 to 4.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](actions/upload-artifact@v2...v4)

---
updated-dependencies:
- dependency-name: actions/upload-artifact
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>

* Fix Dependabot/GitHub actions/actions/upload artifact 4 (#1065)

* fix/pipeline/vscode : use a dedicated job to generate the vscode extension

* feat/pipeline/vscode : use nodejs version 20 instead of 16

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Alidra <[email protected]>
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