Skip to content

Releases: Crown-Commercial-Service/ccs-aws-codepipeline-action

v1.0.2

08 Nov 09:25
598e57e
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.0.1...v1.0.2

v1.0.1

31 Oct 09:05
8458aca
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.0.0...v1.0.1

v1.0.0

24 Oct 12:03
c1e53f6
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.1.4...v1.0.0

v0.1.4

17 Oct 10:46
c9ffa02
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.1.3...v0.1.4

v0.1.3

13 Oct 16:13
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.1.2...v0.1.3

v0.1.2

03 Oct 08:44
a8c74a8
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.1.1...v0.1.2

v0.1.1

14 Sep 09:45
8521b52
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.1.0...v0.1.1

v0.1.0

14 Sep 09:22
4b6240a
Compare
Choose a tag to compare

This action is the same as GitHub Actions x AWS CodePipeline by Zulhilmi Zainudin but with one change. If the triggering of the pipeline fails for any reason, the action will now fail and return the error. I found the original behaviour of the action, escentially, not working but it still saying it was a success quite confusing which is why forked and created this new action.

What's Changed

New Contributors

Full Changelog: https://github.com/tim-s-ccs/aws-codepipeline-action/commits/v0.1.0