Closed
Description
Properties File URL
https://github.com/alexdmiller/shape-mapper/releases/latest/download/shapemapper.txt
Home Page URL
Guidelines Confirmation
- I confirm
https://github.com/alexdmiller/shape-mapper/releases/latest/download/shapemapper.txt
Activity
github-actions commentedon Jan 13, 2025
There was an error in reading your properties file or parsing it.
Please ensure that the URL is correct and the file follows the required format.
Errors when parsing file. Please check all required fields, and file format.
github-actions commentedon Jan 13, 2025
Your properties file was successfully parsed.
A pull request with your contribution has been successfully created.
github-actions commentedon Jan 13, 2025
Your properties file was successfully parsed.
A pull request with your contribution has been successfully created.
SableRaf commentedon Jan 13, 2025
@Stefterv I thought we were asking for a link to the
library.txt
file, rather than thelibrary.properties
file, since the latter isn’t meant to be included in the release artifacts.Shouldn't it be https://github.com/alexdmiller/shape-mapper/releases/download/v0.1.5/shapemapper.txt instead?
Stefterv commentedon Jan 13, 2025
https://github.com/alexdmiller/shape-mapper/releases/latest/download/shapemapper.txt is what it should be
mingness commentedon Jan 13, 2025
I see, the bottom of the issue says the
library.properties
file, which confuses the issue. I'll review the wording of the issues later today.github-actions commentedon Jan 13, 2025
Your properties file was successfully parsed.
A pull request with your contribution has been successfully created.
mingness commentedon Jan 13, 2025
I've updated the url in the issue description to what @Stefterv said it should be. The download url in the database entry is now live.
@alexdmiller there is an inconsistency between the prettyVersion in the library.properties/shapemapper.txt file, which is 1.0.0, and the github release which is v0.1.5 - @Stefterv suggested an improvement to the workflow in the template that would use the release tag and assign it to the prettyVersion in the released *.txt, but that's not there yet - maybe in time for your update. :)
Could you make a patch to your library release, synchronizing the pretty versions? Thanks for working with us as we iron out kinks.
alexdmiller commentedon Jan 15, 2025
Thanks for helping figure it out! I just updated the prettyVersion to match the github release.
github-actions commentedon Jan 15, 2025
Your properties file was successfully parsed.
A pull request with your contribution has been successfully created.
3 remaining items