Closed jscancella closed 1 year ago
Oh, good catch @jscancella. That's all embarrassing :man_facepalming:
For doing the versions, I can create a gh-pages branch, and just create directories for each version. That should be an easy fix. Would that be an ok solution? If so, I can take care of all of it.
Sounds good to me!
I forgot the previous versions were just the README.md
, so I've linked to that in the current branch I have to resolve this issue. But, moving forward, we can just setup a directory for each version using ReSpec old versions, and configure the links to point to the correct version as needed.
Once the incoming PR is merged, I can tag it as 1.3.0, and then pivot to adding the updates for #31, and then tag that 1.4.0 once we get that work merged.
Let me know if that all sounds good.
On https://bagit-profiles.github.io/bagit-profiles-specification/ it has a section:
but if you click on that link it leads to a 404 error.
I also noticed that we have 1.1.0 and 1.2.0 as tags on this repo but no tag for 1.3.0 which is the current version.