Skip to content

build: skip the generated Simple Index folder as an artifact, and use only individual distribution files#1387

Open
jenstroeger wants to merge 1 commit intooracle:mainfrom
jenstroeger:fix-ci-artifacts
Open

build: skip the generated Simple Index folder as an artifact, and use only individual distribution files#1387
jenstroeger wants to merge 1 commit intooracle:mainfrom
jenstroeger:fix-ci-artifacts

Conversation

@jenstroeger
Copy link
Copy Markdown
Contributor

@jenstroeger jenstroeger commented Apr 24, 2026

Summary

The change fixes this failing release job.

Description of changes

The gh release create … command does not handle folders, thus do not add the generated dist/simple-index/ folder as a release artifact.

Related issues

Original breaking change/regression is PR #1377.

Checklist

  • I have reviewed the contribution guide.
  • My PR title and commits follow the Conventional Commits convention.
  • My commits include the "Signed-off-by" line.
  • I have signed my commits following the instructions provided by GitHub. Note that we run GitHub's commit verification tool to check the commit signatures. A green verified label should appear next to all of your commits on GitHub.
  • I have updated the relevant documentation, if applicable.
  • I have tested my changes and verified they work as expected.

…se only individual distribution files

Refs: b3a61b9
Signed-off-by: Jens Troeger <jens.troeger@light-speed.de>
@jenstroeger jenstroeger requested a review from behnazh-w as a code owner April 24, 2026 12:38
@oracle-contributor-agreement oracle-contributor-agreement Bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Apr 24, 2026
@behnazh-w behnazh-w changed the title fix(ci): skip the generated Simple Index folder as an artifact, and use only individual distribution files build: skip the generated Simple Index folder as an artifact, and use only individual distribution files Apr 25, 2026
@jenstroeger
Copy link
Copy Markdown
Contributor Author

Hmm. The run fails because of a new vulnerability CVE-2026-3219 for pip for which there’s no patch and no issue1 yet. So I guess we’ll either ignore this one for now, or wait for a little while until a fix becomes available?

Footnotes

  1. Should we open an issue or report this vulnerability?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

OCA Verified All contributors have signed the Oracle Contributor Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant