Closed wleepang closed 1 year ago
Seems like only the commit, but not the content of the commit is missing, right? In that case, I think it should be noncontroversial to merge
Fantastic! FYI, @patmagee and @wleepang: I have created a release for 1.0.1
: https://github.com/ga4gh/workflow-execution-service-schemas/releases/tag/1.0.1
I have used the autogenerate feature to create the release notes. Given that the issue/PR descriptions are mostly not super descriptive, those aren't very good, but I feel it's better than nothing. Maybe at some point we could clean up the release notes for the different releases, or at leas ttry to keep this a bit cleaner for the latest release (1.1.0
) and moving forward. Personally, I would recommend that we use Conventional Commit messages for commits to the develop
branch. We achive this by squashing commits from PRs from feature branches and using conventional commit messages as PR titles.
The last commit on
master
is the commit that matches the nominal1.0.1
release and the current specification docs per #191 . This pull request merges that release back intodevelop
as the two branches have diverged since then.