It turns out that v0.2.0 was released some time ago, but the Changelog not updated to note the release date. Then I came blundering in, saw that (as I read the Changelog) there had been no v0.2.0 release yet, deleted the apparently pointing-into-hyperspace v0.2.0 tag, and prepared a new release – also v0.2.0 – on the dev branch.
Only as I was on the point of making the actual NPM release did Zak, many timezones behind me, come online and prevent the disaster.
Much of that now needs to be undone and redone. Sigh.
Only when that has happened can I finally release v0.3.0, which will include <ControlledVocab> (STSMCOM-6). And only after that will Zak be able to roll a v1.0.0 that has the correct True Name (STSMCOM-7).
Resolved, as far as I can tell. The Changelog and Jira's notion of the v0.2.0 release are now both set for a week go, when Zak did what seems to be the final merge before the release. And I have made release v0.3.0 to include <ControlledVocab>.
Well, this is horrible.
It turns out that v0.2.0 was released some time ago, but the Changelog not updated to note the release date. Then I came blundering in, saw that (as I read the Changelog) there had been no v0.2.0 release yet, deleted the apparently pointing-into-hyperspace v0.2.0 tag, and prepared a new release – also v0.2.0 – on the
devbranch.Only as I was on the point of making the actual NPM release did Zak, many timezones behind me, come online and prevent the disaster.
Much of that now needs to be undone and redone. Sigh.
Only when that has happened can I finally release v0.3.0, which will include
<ControlledVocab>(STSMCOM-6). And only after that will Zak be able to roll a v1.0.0 that has the correct True Name (STSMCOM-7).