Skip to content

Releases: rwx-research/setup-captain

Release v1.2.1

29 Jan 20:21
f8b1cbf
Compare
Choose a tag to compare
Update action to run with node 20 (#16)

GitHub has deprecated Node 16 in Actions. Workflows using this action
are throwing a deprecation warning since it's using Node 16


https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20

---------

Co-authored-by: Kyle Thompson <[email protected]>

Release v1.2.0

12 Apr 15:31
cf0d9ca
Compare
Choose a tag to compare
Support unstable releases (#15)

Supports unstable releases per
https://github.com/rwx-research/captain/pull/32

Release v1.1.7

07 Feb 13:55
faf31d2
Compare
Choose a tag to compare
Reference the new releases URLs (#13)

Release v1.1.6

02 Feb 19:50
6881eaa
Compare
Choose a tag to compare
Fetch the -v1 url instead of doing the version lookup (#12)

Now that we're publishing the -v1 binaries directly, we can simply
download those.

Release v1.1.5

01 Feb 21:24
f31865a
Compare
Choose a tag to compare
Make latest an alias to v1 to deprecate and remove it (#11)

Release v1.1.4

25 Jan 16:55
7998e28
Compare
Choose a tag to compare
Make the v prefix on version numbers optional (#10)

Release v1.1.3

20 Dec 16:06
2d90234
Compare
Choose a tag to compare
Output the version after installing (#9)

This will make debugging with customers easier. I also believe that
having the action output something about its success helps give
confidence that things are working as expected.

Release v1.1.2

15 Nov 20:43
ce705f0
Compare
Choose a tag to compare
Add link to documentation (#8)

Release v1.1.1

14 Nov 21:06
02c1131
Compare
Choose a tag to compare

This release installs v1 of the Captain CLI by default.

Release v1.1.0

14 Nov 20:46
506490d
Compare
Choose a tag to compare
Allow to install captain by major version lookup (#5)

This change allows a user to install the latest `v1.x.x` version of the
CLI by referring to it as `v1`. Also, this is now the new default when
no version number was supplied. Explicitly setting `latest` as the
version number continues to work.

> **Warning**: This is currently broken and should not be merged until
we actually have a `v1` version of the CLI released.

Further, this technically constitutes a breaking change to the public
API of this action and would require a major version change as we follow
semantic versioning. However, the main motivation behind changing the
default behaviour was to align the `v1` version of this action with the
`v1` release of the CLI, so a major version bump would defeat the
purpose here.

Co-authored-by: Dan Manges <[email protected]>