Prepare repository for open-source release#6
Conversation
- Switch license from MIT to Apache 2.0 (Datadog standard) - Add NOTICE, CONTRIBUTING.md, LICENSE-3rdparty.csv, RELEASING.md - Add PR and issue templates under .github/ - Add license headers to all files - Add release workflow that creates a GitHub Release and updates the floating major version tag (e.g. v2) on each semver tag push Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
The existing test workflow requires Node.js and a real API key secret. It will be replaced with a proper OS-matrix workflow in a follow-up PR. Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 771468c323
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| on: | ||
| push: | ||
| tags: | ||
| - 'v[0-9]+.[0-9]+.[0-9]+' |
There was a problem hiding this comment.
Match release tags with a valid GitHub Actions glob
The release trigger pattern v[0-9]+.[0-9]+.[0-9]+ is regex-style, but on.push.tags is evaluated as a glob pattern, so the + characters are treated literally; as a result, normal tags like v2.1.0 will not match and the Release workflow will not run. This blocks both GitHub Release creation and the floating major-tag update for all standard semver releases.
Useful? React with 👍 / 👎.
Summary
NOTICE,CONTRIBUTING.md,LICENSE-3rdparty.csv,RELEASING.md.github/v2) on each semver tag push;update-major-tagjob depends onreleaseso the tag only moves after the release is successfully createdTest plan
LICENSE,NOTICE,CONTRIBUTING.md,LICENSE-3rdparty.csv,RELEASING.md🤖 Generated with Claude Code