Release a first release? ("0.1.0")

[zeeshanlakhani]

Extending on #14.

@MarcoIeni I'm suffering from a similar issue that includes way more uncommitted files (on a first release):

https://github.com/ipvm-wg/homestar/actions/runs/6464670097/job/17549663658#step:28:150

I've added https://github.com/ipvm-wg/homestar/blob/main/release-plz.toml, but avoided allow-dirty/publish-allow-dirty, as it seems to want to capture things unrelated to the packages I actually want to release, i.e. all the top-level .md's, dockers, examples. I'm probably just messing something up, and I know MarcoIeni/release-plz#721 is not there yet; however, how would you suggest I go about this for a first release?

Additionally, every variant of a PR I create seems to want to delete all the "uncommitted" files. I could fix this manually for the first release, maybe?

[MarcoIeni]

Hi!
In https://github.com/ipvm-wg/homestar/blob/main/.github/workflows/release.yml I noticed that you are using rust-cache before installing the toolchain. But you should first install the toolchain and than use the cache from my understanding and their docs.

Not sure if related with your issue.

Can you try running https://github.com/ipvm-wg/homestar/blob/b0bda83236f946081aca99c62eb3b0c71f11312b/.github/workflows/release.yml#L53 in another job? Probably it's creating some files and so it leaves the directory dirty.
You can say that release-plz depends on the dry-run job.

[zeeshanlakhani]

@MarcoIeni sure on both fronts; however, in running release-plz locally, same config, w/ release-plz release-pr ..., I'm also getting the same set of uncommitted things (top-levels, etc). So, this is not just action related it seems.

Error: the working directory of this project has uncommitted changes. Please commit or stash these changes...

What do you think? Seems like if it happens locally it's another issue @MarcoIeni.

[MarcoIeni]

Sorry for the delay, I'm at EuroRust and i didn't have time to look into this yet. I'll try to have a look this weekend.

[MarcoIeni]

After #1036 and applying this change, release-plz update works locally:

$ release-plz update
...
$ git status
On branch main
Your branch is ahead of 'origin/main' by 1 commit.
  (use "git push" to publish your local commits)

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	homestar-core/CHANGELOG.md
	homestar-runtime/CHANGELOG.md
	homestar-wasm/CHANGELOG.md

nothing added to commit but untracked files present (use "git add" to track)

[zeeshanlakhani]

awesome and thank you @MarcoIeni. Will test this myself shortly. I'll add one fix to your PR there and merge. Thanks for being so helpful!

[zeeshanlakhani]

Guessing you'll cut a new action release too to get the version update (if it works that way)?

[MarcoIeni]

Yes, I'm on it 😎
Should be ready in a couple of hours.

[MarcoIeni]

released now. Enjoy!