Rebranding Progress and Updates

[eskultety]

We want to inform everyone that our a rebranding process (based on https://github.com/orgs/hermetoproject/discussions/824) has officially begun! This means you may start noticing changes to the various references throughout the repository and ultimately, to the repository name and release artifacts.

What Will Change?

• the project name and any related branding will be updated across the codebase, documentation, and release artifacts.
• some file names, folder structures, and configuration options will be adjusted to reflect the new name

Backward compatibility will be maintained as much as possible, however, there may be some breaking changes, we'll make sure to communicate them properly.

What Does This Mean for You?

If you are actively developing or contributing, please be mindful of ongoing changes to the code base and check this discussion for important updates. Until the rebranding is complete releases will include a hybrid of both old and new naming conventions as we transition gradually. As for using the project (either directly or via the built docker container image) you'll continue using it the old way using the old name, so nothing changes for the time being.

How Can You Help?

We appreciate feedback, suggestions, and testing throughout this process. Feel free to:

• comment on this discussion if you encounter any issues or have suggestions.
• open issues if you notice any inconsistencies or problems related to the rebranding.
• help update documentation or test new builds if you’re able!

Timeline and Progress

We will keep this discussion updated with progress and any major changes as they happen.
Stay tuned, and thank you for your continued support and understanding! 🙏

[eskultety]

I'd like to announce that we have successfully completed the rebranding effort and that starting with release 0.23.0 we refer to our project/tool by the new name - hermeto!
From functional perspective, this change should be largely transparent (the container image aside) to users because we have put in a legacy entrypoint so that all current deployments invoking the old named 'cachi2' tool would continue working. We will maintain the legacy entrypoint for a while (exact deprecation date TBD), we'll make sure to announce the deprecation appropriately in advance.

That all said, despite the best of efforts there may still be references to the old name (i.e. cachi2) here and there in the code base which we'll gradually address and get rid of, but you can stay at rest, it's nothing functional, merely a minor cosmetic defect :). We'll be dropping the landing page rebranding notice soon as well.