Skip to content

Conversation

juxtin
Copy link
Contributor

@juxtin juxtin commented Jul 2, 2025

The version was previously set to 1.0.0, so I'm going to take this opportunity to start doing things the right way.

@juxtin juxtin requested review from a team as code owners July 2, 2025 19:40
@juxtin juxtin requested review from adrienpessu and aegilops and removed request for a team July 2, 2025 19:40
@@ -1,6 +1,6 @@
{
"name": "component-detection-action",
"version": "1.0.0",
"version": "0.0.7",

Choose a reason for hiding this comment

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

Are we moving backwards?!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

According to this, yes. We've been using the default "1.0.0" since the project was started, even though we've never shipped an actual 1.0.0 release.

Choose a reason for hiding this comment

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

Never mind, I looked at the releases tap.

@juxtin juxtin merged commit 64db6d9 into main Jul 2, 2025
5 checks passed
@juxtin juxtin deleted the juxtin/prep-007 branch July 2, 2025 19:54
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