generated from honeycombio/.github
-
Notifications
You must be signed in to change notification settings - Fork 15
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
maint: Match semantic convention version to SDK semantic conventions (#…
…60) ## Which problem is this PR solving? - it's easy to mismatch semantic convention versions (see notes in #59 ) ## Short description of the changes - Drop our version of semantic conventions to 1.17 to match those used in the imported otel-go package - Update the README to clarify versions in use (note old semconv listed because that's in current available release) - Update releasing notes to remember to adjust README if versions change, and some other cleanup for consistency to other repos - Add simple unit test for checking semantic convention version against otel-go imported package semantic convention - Add unit tests for resource detector from core (WithHost) and contrib (lambda) to confirm no schema error ## How to verify that this has the expected result Using a detector on the same version should work. These tests should fail if you change the semantic convention version back to 1.18.0 in the imports.
- Loading branch information
1 parent
7129f53
commit d1e3a56
Showing
6 changed files
with
70 additions
and
35 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,14 @@ | ||
# Releasing | ||
|
||
- Update `version.go` with version of release. | ||
- Update `CHANGELOG.md` with the changes since the last release. | ||
- If the new release updates the OpenTelemetry SDK and/or Semantic Convention versions, update the `Latest release built with` section in the [README](./README.md). | ||
- Update `CHANGELOG.md` with the changes since the last release. Consider automating with a command such as these two: | ||
- `git log $(git describe --tags --abbrev=0)..HEAD --no-merges --oneline > new-in-this-release.log` | ||
- `git log --pretty='%C(green)%d%Creset- %s | [%an](https://github.com/)'` | ||
- Commit changes, push, and open a release preparation pull request for review. | ||
- Once the pull request is merged, fetch the updated `main` branch. | ||
- Apply a tag for the new version on the merged commit (e.g. `git tag -a v1.2.3 -m "v1.2.3"`) | ||
- Push the tag upstream (this will kick off the release pipeline in CI) e.g. `git push origin v1.2.3` | ||
- Open the draft GitHub release created as part of CI publish steps and "generate release notes" | ||
- Publish the github draft release and this will kick off publishing to GitHub. | ||
- Ensure that there is a draft GitHub release created as part of CI publish steps. | ||
- Click "generate release notes" in GitHub for full changelog notes and any new contributors | ||
- Publish the GitHub draft release - if it is a prerelease (e.g. beta) click the prerelease checkbox. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters