Skip to content

Prepare repository for open-source release#6

Merged
CarlosNietoP merged 2 commits into
mainfrom
carlos.nietopetinal/open-source-prep
Feb 27, 2026
Merged

Prepare repository for open-source release#6
CarlosNietoP merged 2 commits into
mainfrom
carlos.nietopetinal/open-source-prep

Conversation

@CarlosNietoP

Copy link
Copy Markdown
Contributor

Summary

  • 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 source files
  • Add release workflow that creates a GitHub Release and updates the floating major version tag (e.g. v2) on each semver tag push; update-major-tag job depends on release so the tag only moves after the release is successfully created

Test plan

  • Verify all open-source checklist files are present: LICENSE, NOTICE, CONTRIBUTING.md, LICENSE-3rdparty.csv, RELEASING.md
  • Verify PR and issue templates appear when opening a new PR/issue on GitHub
  • Verify release workflow triggers on a semver tag push and creates a GitHub Release with auto-generated notes
  • Verify floating major tag is updated after the release is created

🤖 Generated with Claude Code

- 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]>
@CarlosNietoP
CarlosNietoP marked this pull request as ready for review February 27, 2026 11:09
@CarlosNietoP
CarlosNietoP requested review from a team as code owners February 27, 2026 11:09

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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]+'

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

@CarlosNietoP
CarlosNietoP merged commit 73e61d5 into main Feb 27, 2026
3 checks passed
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