Announcing scryer-prolog 0.9.2

[mthom]

It's time for another release! Version 0.9.2 brings improved disjunction compilation, a new implementation of the HTTP libraries, compilation support for 32-bit systems, many bug fixes, further call/N performance improvements, a new FFI library, increased syntactic conformity, and probably additional things I've since forgotten. cargo publish --dry-run isn't working though the ordinary cargo run [--release] works fine. I have no idea why.. I'm still trying to figure it out.

[mvolkmann]

I pulled the latest on the master branch, ran cargo build --release, and entered scryer-prolog -v. It outputs v0.9.1-523-gc65d1204. Should that begin with v0.9.2?

[UWN]

Same here:

ulrich@TU-Wien:/opt/gupu/scryer-prolog$ git describe
v0.9.1-523-gc65d1204
ulrich@TU-Wien:/opt/gupu/scryer-prolog$ cargo build --release
   Compiling scryer-prolog v0.9.1 (/opt/gupu/scryer-prolog)

[triska]

I think the relevant tag still needs to be created and pushed?

As in:

$ git tag v0.9.2
$ git push --tags

[mthom]

ok, I followed these instructions. git describe still returns v0.9.1-524-g78b35dc5 for me. but at least it's not off on a separate branch or whatever weirdness that was.

[triska]

I think it is now correctly tagged, git describe shows the intended tag if we specify the --tags option:

$ git describe --tags
v0.9.2

Thank you a lot to everyone who contributed, and congratulations on this awesome release!

[triska]

I now found the following, from git help tag:

       Annotated tags are meant for release while lightweight tags are meant
       for private or temporary object labels. For this reason, some git
       commands for naming objects (like git describe) will ignore lightweight
       tags by default.

OPTIONS
       -a, --annotate
           Make an unsigned, annotated tag object

So, the -a flag must be used when creating a tag, in order for git describe to show this tag!

[mvolkmann]

I see the new tag now when I enter git describe --tags, but after running cargo build --release and entering scryer-prolog -v, I still get v0.9.1-524-g78b35dc5.

[infogulch]

I had to git pull --tags -f because I had the old tag. Now git describe shows v0.9.2, and after building scryer-prolog --version shows v0.9.2.

[mvolkmann]

I ran cargo clean and then cargo build --release again. Now scryer-prolog --version outputs v0.9.2. So doing the clean resolved the issue.

[infogulch]

Congratulations!

Glad to see that the release job worked and Scryer now has binaries published with its releases. 😄