Wait, wait? "Proposal: make project-name persistent, #745" got implemented with this?! 🎉

@glensc yep 👍

Looks feels like very secretive, not even references in pull requests or changelogs with descriptions.

however, found the pr with changes:

• Update spec and implement project name compose-spec/compose-go#231

and then description of the changes:

• introduce top-level name compose-spec/compose-spec#206

We can't say it was secretive 😅 , the Compose Specification is public and the #745 where mentioned in this Compose Spec update PR

I tried to say it feels secretive, as #745 was closed automatically, and it refers to #9219, which has some technical description, not seemingly related to the problem at hand. could the original issue be closed by accident I was wondering?

so I had to find what that compose-go is, and their 1.1.0 release notes also said nothing, and it also has no changelog, so had to visit their commits to find a related pull request ...

What would feel better is a post there saying something along "Hooray, we have released docker-compose 1.32 (includes docker-go 1.1.0) with the support of "name", it will be available on 1st of April and if you use docker desktop then it will be bundled with next update"

:)

Ok thanks for your feedback, I updated the compose-go release notes
And we didn't release a new version of Compose right now 😅