Update versions to latest

[lorypelli]

Let me know if you want something to not be updated, but I think it's better to update everything...

[Jacalz]

Have you built the images locally and verified that they work?

[lorypelli]

Have you built the images locally and verified that they work?

I'm having troubles make go running locally, I don't know why it doesn't want to set the PATH on linux
Also having troubles running the docker image...

[lorypelli]

Have you built the images locally and verified that they work?

I need to change sha256

[Jacalz]

You should not knowingly open a PR with untested changes. That's very bad practice. If something is work in progress, at least open as a draft

[lorypelli]

You should not knowingly open a PR with untested changes. That's very bad practice. If something is work in progress, at least open as a draft

Now I managed to test

[lorypelli]

@Jacalz building works correctly

[Bluebugs]

I would prefer one pr for each change and with a descriptive change in each case (like 'updating fyne to v2.4.3')

[andydotxyz]

Thanks for this, but watch you don't remove important content.

Has this combination of versions worked well for you?

[andydotxyz]

I would prefer one pr for each change and with a descriptive change in each case (like 'updating fyne to v2.4.3')

Surely that is a lot of overhead for version bumps. If you really need it a separate commit for each managed project, but not a whole PR?

[lorypelli]

Thanks for this, but watch you don't remove important content.

Has this combination of versions worked well for you?

I would like to update also zig version but I wasn't able to find sha256, so I restored it to dev, but I didn't add back the comment, I will try to find the sha but now I don't have time...

[lorypelli]

I added the comment back for now, you can merge it if you want, it builds correctly

[lorypelli]

Actually, I wasn't able to run any command inside of the docker container, it wasn't giving output of them, idk why so I recommend you test this locally by yourself

[lorypelli]

I was able to find it

[Bluebugs]

Updating zig is a high risk operation. Have you tried to build a few application with this new image using fyne-cross and tested them on their target environment.

[lorypelli]

Updating zig is a high risk operation. Have you tried to build a few application with this new image using fyne-cross and tested them on their target environment.

If you think it can be an issue, let me know and I will revert the change and make another pull request when I will be able to make sure everything works with it

[lorypelli]

ok, for now I reverted it, let me know if you are able to do some tests with it

[Jacalz]

I would prefer one pr for each change and with a descriptive change in each case (like 'updating fyne to v2.4.3')

Surely that is a lot of overhead for version bumps. If you really need it a separate commit for each managed project, but not a whole PR?

I agree. One commit for each would be more sensible.

[andydotxyz]

@lorypelli lorypelli requested a review from andydotxyz 3 days ago

I'm not the right person to review this - but others are around who know it well.

[Jacalz]

Sorry @lorypelli, I think this got superseded by #43. Apologies.

[Jacalz]

I closed this now but you are more than welcome to open a new PR for that workflow misspelling. I don't think there is any need to update fixuid because the latest release of fyne-cross doesn't use it as far as I know.