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

misc(build): use git-describe for build bundle version header #14347

Merged
merged 5 commits into from
Sep 7, 2022

Conversation

connorjclark
Copy link
Collaborator

@connorjclark connorjclark commented Sep 2, 2022

Learned about git-describe this week.

Gives us this header at the top of our bundles: Lighthouse v9.5.0-248-gad6f1dba7 (Sep 02 2022) (prev: Lighthouse v9.5.0 <whatever the commit sha is> (Sep 02 2022)). Note that gad6f1dba7 is a reference to the commit's first git object, not the commit itself–but the entire thing is itself a valid ref specifier (in other words, git show v9.5.0-248-gad6f1dba7 works but git show gad6f1dba7 is nonsense)

We don't ship non-tagged versions most of the time, but we do regularly to LR's canary feed.

@@ -251,6 +254,5 @@ if (esMain(import.meta)) {
}

export {
COMMIT_HASH,
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

was not used

@paulirish
Copy link
Member

fwiw this describe string means its 248 commits past the v9.5.0 tag. (which it is)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants