Closed shogo82148 closed 4 months ago
A new step named Generate artifact attestation
has been integrated into the GitHub Actions workflow within the .github/workflows/release.yml
file. This step employs the actions/attest-build-provenance@v1
action to generate attestations for artifacts located in the dist
directory, specifically during release events. This enhancement bolsters the security and provenance of the release artifacts.
Files | Summary |
---|---|
.github/workflows/release.yml |
Added the Generate artifact attestation step using actions/attest-build-provenance@v1 to attest release artifacts in the dist directory. |
sequenceDiagram
participant Developer
participant GitHubActions as GitHub Actions
participant ActionsAttest as actions/attest-build-provenance@v1
Developer->>GitHubActions: Push release changes
GitHubActions->>GitHubActions: Trigger workflow on release
GitHubActions->>ActionsAttest: Execute step 'Generate artifact attestation'
ActionsAttest->>GitHubActions: Attestation of artifacts in 'dist' directory
GitHubActions-->>Developer: Workflow status and attestation results
In the code’s quiet night,
Artifacts take their flight,
A step to attest,
Ensuring the best,
Provenance shines so bright.
🌙✨
[!TIP]
Early access features: disabled
We are currently testing the following features in early access: - **OpenAI `gpt-4o` model for code reviews and chat**: OpenAI claims that this model is better at understanding and generating code than the previous models. We seek your feedback over the next few weeks before making it generally available. Note: - You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file. - Please join our [Discord Community](https://discord.com/invite/GsXnASn26c) to provide feedback and report issues. - OSS projects are always opted into early access features.
Summary by CodeRabbit