Skip to content

Conversation

@avidal
Copy link
Collaborator

@avidal avidal commented Jul 10, 2025

This patch sets up an action release pipeline on merges to main which
resembles the gitlab release pipeline.

On a merge to main, the workflow kicks in and (assuming everything
builds and tests well), updates the action branch with the contents of
action-template/.

The workflow leverages the bundled action, which ensures that, at the
very least, we cannot produce a tagged release of the action that cannot
at least release itself.

Note that the action branch contains the binaries built earlier in the
workflow to avoid having to run a composite action.

@datadog-datadog-prod-us1
Copy link

datadog-datadog-prod-us1 bot commented Jul 10, 2025

✅ Libraries

ℹ️ Info

🎉 All green!

📚 No new vulnerable libraries detected

This comment will be updated automatically if new data arrives.

🔗 Commit SHA: caef22f | Was this helpful? Give us feedback!

@avidal avidal changed the title scaffold an action release workflow ci: set up an action release pipeline Jul 15, 2025
This patch sets up an action release pipeline on merges to main which
resembles the gitlab release pipeline.

On a merge to main, the workflow kicks in and (assuming everything
builds and tests well), updates the `action` branch with the contents of
`action-template/`.

The workflow leverages the bundled action, which ensures that, at the
very least, we cannot produce a tagged release of the action that cannot
at least release itself.

Note that the action branch contains the binaries built earlier in the
workflow to avoid having to run a composite action.
@avidal avidal merged commit 691b7c3 into main Jul 15, 2025
7 checks passed
@avidal avidal deleted the release-action branch July 15, 2025 19:22
avidal added a commit that referenced this pull request Jul 15, 2025
This patch sets up an action release pipeline on merges to main which
resembles the gitlab release pipeline.

On a merge to main, the workflow kicks in and (assuming everything
builds and tests well), updates the `action` branch with the contents of
`action-template/`.

The workflow leverages the bundled action, which ensures that, at the
very least, we cannot produce a tagged release of the action that cannot
at least release itself.

Note that the action branch contains the binaries built earlier in the
workflow to avoid having to run a composite action.
avidal added a commit that referenced this pull request Jul 15, 2025
This patch sets up an action release pipeline on merges to main which
resembles the gitlab release pipeline.

On a merge to main, the workflow kicks in and (assuming everything
builds and tests well), updates the `action` branch with the contents of
`action-template/`.

The workflow leverages the bundled action, which ensures that, at the
very least, we cannot produce a tagged release of the action that cannot
at least release itself.

Note that the action branch contains the binaries built earlier in the
workflow to avoid having to run a composite action.
avidal added a commit that referenced this pull request Jul 15, 2025
This patch sets up an action release pipeline on merges to main which
resembles the gitlab release pipeline.

On a merge to main, the workflow kicks in and (assuming everything
builds and tests well), updates the `action` branch with the contents of
`action-template/`.

The workflow leverages the bundled action, which ensures that, at the
very least, we cannot produce a tagged release of the action that cannot
at least release itself.

Note that the action branch contains the binaries built earlier in the
workflow to avoid having to run a composite action.
avidal added a commit that referenced this pull request Jul 15, 2025
This patch sets up an action release pipeline on merges to main which
resembles the gitlab release pipeline.

On a merge to main, the workflow kicks in and (assuming everything
builds and tests well), updates the `action` branch with the contents of
`action-template/`.

The workflow leverages the bundled action, which ensures that, at the
very least, we cannot produce a tagged release of the action that cannot
at least release itself.

Note that the action branch contains the binaries built earlier in the
workflow to avoid having to run a composite action.
avidal added a commit that referenced this pull request Jul 15, 2025
This patch sets up an action release pipeline on merges to main which
resembles the gitlab release pipeline.

On a merge to main, the workflow kicks in and (assuming everything
builds and tests well), updates the `action` branch with the contents of
`action-template/`.

The workflow leverages the bundled action, which ensures that, at the
very least, we cannot produce a tagged release of the action that cannot
at least release itself.

Note that the action branch contains the binaries built earlier in the
workflow to avoid having to run a composite action.

Co-authored-by: Alex Vidal <alex.vidal@datadoghq.com>
avidal added a commit that referenced this pull request Jul 15, 2025
This patch sets up an action release pipeline on merges to main which
resembles the gitlab release pipeline.

On a merge to main, the workflow kicks in and (assuming everything
builds and tests well), updates the `action` branch with the contents of
`action-template/`.

The workflow leverages the bundled action, which ensures that, at the
very least, we cannot produce a tagged release of the action that cannot
at least release itself.

Note that the action branch contains the binaries built earlier in the
workflow to avoid having to run a composite action.

Co-authored-by: Alex Vidal <alex.vidal@datadoghq.com>
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