Branch / Tag zig v0.14

[failingprovince]

Hi,

this commit 3aa266d5787b4ca1f2792b6cd6ec7f36f2a79fbf is the last commit before breaking change that stops support for zig 0.14.

I think it would make sense to tag it or create a branch, so people can zig fetch it.

[yamashitax]

I think you might’ve linked the wrong commit.

[failingprovince]

Thanks, I corrected the mistake.

[yamashitax]

Thanks, I corrected the mistake.

What is a "lady commit" in this context?

[failingprovince]

I swear I’m not doing this on purpose😂
I got multiple languages on my keyboard and probably the spelling checker did some magic and turned “last” into “lady”.

[yamashitax]

Have you updated to zig version 14.1?

[yamashitax]

I would also suggest that you keep your zig version to the one recommended in build.zig.zon

[failingprovince]

Have you updated to zig version 14.1?

Yes, I did. Still, patch releases are backward compatible with major releases, so that's not the problem.

I would also suggest that you keep your zig version to the one recommended in build.zig.zon

I don't really understand what you mean.

• The build.zig.zon auto-generated by my compiler?
• The build.zig.zon of zmpl?

Either way, imho it makes completely sense to tag commit 3aa266 as it's the last commit before a breaking change that completely breaks any 0.14.x compatibility, since standard library's AST module used in the following commit has been rewritten in master.

For the moment I just zig fetch --save git+https://github.com/jetzig-framework/zmpl#3aa266d5787b4ca1f2792b6cd6ec7f36f2a79fbf, which works completely fine, but I had to work my way through the commit history to get that commit, I just wanted make things easier for who is coming next.

[Cohors1316]

Im just seeing this. About to tag this for 0.15 after I finish and make a flake for it. Jetzig has working branch for 0.14, if you still want a 0.14 tag I can tag the one used there.