Skip to content

Conversation

@stayallive
Copy link
Collaborator

@stayallive stayallive commented Sep 22, 2025

As mentioned in #1, we should cleanup the timestamp and COMPOSER_ROOT_VERSION. I've opted to not bother with the timestamp, and the version is only set when craft creates a release.

In PRs and normal development we use 0.0.0 to get somewhat reproducible builds. We could use Docker to get builds that are also reproducible locally since it depends on the exact PHP version and some other environment things. But not sure we need to go that hard.

@stayallive stayallive self-assigned this Sep 22, 2025
@stayallive stayallive marked this pull request as ready for review September 22, 2025 10:23
Copy link
Contributor

@Litarnus Litarnus left a comment

Choose a reason for hiding this comment

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

LGTM!

I'm not sure if we really need a real version number since we only care about file changes but I guess it also doesn't hurt to have it

@stayallive
Copy link
Collaborator Author

Yeah I also started with just leaving it at 0.0.0 but I guess it could help if we need to debug and I believe we can show the version in the output... (tbd in another PR).

@stayallive stayallive merged commit 5ae24c4 into main Sep 22, 2025
7 checks passed
@stayallive stayallive mentioned this pull request Sep 22, 2025
14 tasks
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.

3 participants