Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update specification repo after 1.7.0 release #798

Merged
merged 1 commit into from
Oct 1, 2021

Conversation

tigrannajaryan
Copy link
Member

This PR is done by following instructions posted at
#719

This PR is done by following instructions posted at
open-telemetry#719
@tigrannajaryan tigrannajaryan requested a review from a team October 1, 2021 10:32
Copy link
Contributor

@chalin chalin left a comment

Choose a reason for hiding this comment

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

Perfect!

@chalin chalin merged commit f51f526 into open-telemetry:main Oct 1, 2021
@chalin
Copy link
Contributor

chalin commented Oct 1, 2021

Thanks for the PR @tigrannajaryan!

@chalin
Copy link
Contributor

chalin commented Oct 1, 2021

@tigrannajaryan - is the process you used to submit the updated spec version convenient enough for you? Note that there's a script specifically for updating the spec (i.e., schemas):

$ npm run schemas:update

@tigrannajaryan
Copy link
Member Author

@tigrannajaryan - is the process you used to submit the updated spec version convenient enough for you? Note that there's a script specifically for updating the spec (i.e., schemas):

$ npm run schemas:update

I run npm run submodule:update content-modules/opentelemetry-specification directly, didn't know about schemas:update, but it is very simple to do anyway, thanks!

Ideally we want to automate this so that after a spec release is done this repo is updated automatically, but manual works for now too.

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