build: ensure console scripts are available on PATH during build

[gaborbernat]

Resolves #214.

[FFY00]

Thank you! I just have some minor comments.

[gaborbernat]

@layday @FFY00 I think now I've addressed all raised concerns 👍🏻 and CI is passing. @FFY00 do you want to add the changelog now?

[layday]

LGTM, thanks for working on this.

[gaborbernat]

@FFY00 can we get this out the door?

[FFY00]

Thanks 😊

[gaborbernat]

Considering this is a critical bugfix can we do a release with what we have (0.1.1?), thanks!

[FFY00]

Just a FYI, since we now have a changelog you can add an entry to CHANGELOG.rst in the PR. The order is supposed to be by relevance. I did it manually now.

[FFY00]

Considering this is a critical bugfix can we do a release with what we have (0.1.1?), thanks!

We can have a new release sure, but because there were a few behavior changes I think it should be 0.2.0, let's save 0.1.X for bugfixes.

[gaborbernat]

Sure, I generally reserve minor versions for feature additions, not bug fixes, but don't mind.

The order is supposed to be by relevance.

How do you determine relevance? This feels very subjective and open for debate. I'd suggest something more objective.

[FFY00]

Sure, I generally reserve minor versions for feature additions, not bug fixes, but don't mind.

I am generally inclined to also increment minor versions when there are behavior changes that might break stuff, which is the case with us now resolving dependencies recursively.

How do you determine relevance? This feels very subjective and open for debate. I'd suggest something more objective.

Yes, it's subjective. I am not very picky here. The goal is to try to make things easier for users, if that requires two more sentences exchanged between maintainers, I am fine with that, if this becomes more we should revisit.

[FFY00]

Also, there was a breaking change https://pypa-build.readthedocs.io/en/stable/changelog.html#breaking-changes.