Skip to content

[pull] main from actions:main #15

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

Open
wants to merge 425 commits into
base: main
Choose a base branch
from
Open

[pull] main from actions:main #15

wants to merge 425 commits into from

Conversation

pull[bot]
Copy link

@pull pull bot commented Feb 2, 2024

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.3)

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot added the ⤵️ pull label Feb 2, 2024
@pull pull bot added the merge-conflict Resolve conflicts manually label Feb 27, 2024
joshmgross and others added 28 commits October 2, 2024 14:30
* Explicitly import `crypto`

* Add release notes for 1.11.1

* Fix crypto mock in test

* Fix `crypto` mock

* Lint
Use native `crypto` package from node
`@actions/attest`: bump @sigstore/sign from 2.3.2 to 3.0.0
`@actions/attest`: bump @actions/core from 1.10.1 to 1.11.1
`@actions/attest`: prep release of @actions/attest v1.5.0
When using some monorepo-related tools (like [changesets](https://github.com/changesets/changesets)),
the produced tags have a special format that includes `@` character.

For example, a `foo` package on a monorepo will produce Git tags looking
like `[email protected]` if using changesets.

When used in combination with `actions/attest-build-provenance`, the
action was not properly re-crafting the tag in `buildSLSAProvenancePredicate` because
it was always splitting the workflow ref by `@` and taking the second
element.

This result in this error on CI:

```
Error: Error: Failed to persist attestation: Invalid Argument - values do not match: refs/tags/foo != refs/tags/[email protected] - https://docs.github.com/rest/repos/repos#create-an-attestation
````

This PR slightly update the logic there, and rather take "everything
located after the first '@'". This shouldn't introduce any breaking
change, while giving support for custom tags.

I've added the corresponding test case, it passes, however I couldn't
successfully run the full test suite (neither on `main`). Looking
forward for CI outcome.

Thanks in advance for the review 🙏.
`@actions/attest`: Support multi-subject attestations
Handle tags containing "@" character in `buildSLSAProvenancePredicate`
`@actions/attest`: Release notes for v1.5.0 release
Copilot AI and others added 30 commits July 14, 2025 10:32
…to errors

- Update isFeatureAvailable() to leverage ACTIONS_CACHE_SERVICE_V2 feature flag
- For v2: check ACTIONS_RESULTS_URL availability
- For v1: check either ACTIONS_CACHE_URL or ACTIONS_RESULTS_URL availability
- Change warning logs to error logs for cache failures
- Add comprehensive tests covering all scenarios

Co-authored-by: Link- <[email protected]>
- Update restoreCacheV2.test.ts, restoreCache.test.ts, saveCacheV2.test.ts, and saveCache.test.ts
- Change test expectations from core.warning to core.error for cache operation failures
- All tests now pass successfully

Co-authored-by: Link- <[email protected]>
Explicit logging of cache key and restore key matches
Improve cache service availability determination and implement conditional error logging
Move `@protobuf-ts/plugin` to dev dependencies
Reintroduce `@protobuf-ts/runtime-rpc` as a runtime dependency
Update cache package compilation step to only install runtime dependencies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⤵️ pull merge-conflict Resolve conflicts manually
Projects
None yet
Development

Successfully merging this pull request may close these issues.