Bump psu version to 1.0.3

Update CHANGELOG
This commit is contained in:
Tortue Torche 2020-01-09 15:12:37 +01:00 committed by Tortue Torche
parent 1334a77bb2
commit 7872bb7e7d
4 changed files with 20 additions and 8 deletions

View File

@ -6,6 +6,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased]
## [1.0.3] - 2020-01-09
### Added
- Cleaning old Docker repository builds tags via [GitLab API](https://docs.gitlab.com/12.6/ee/api/container_registry.html#delete-repository-tags-in-bulk)
### Changed
- Use [Traefik 2.1](https://docs.traefik.io/v2.1/) instead of [Traefik 1.7](https://docs.traefik.io/v1.7/) for testing
### Fixed
- Build script for the latest stable git tag of a given git branch
## [1.0.2] - 2019-12-10
### Added
- Test <abbr title="Portainer Stack Utils">PSU</abbr> with Portainer [1.23.0](https://app.swaggerhub.com/apis/deviantony/Portainer/1.23.0) API
@ -55,7 +65,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Debug mode
- Strict mode
[Unreleased]: https://gitlab.com/psuapp/psu/compare/v1.0.2...master
[Unreleased]: https://gitlab.com/psuapp/psu/compare/v1.0.3...1-0-stable
[1.0.3]: https://gitlab.com/psuapp/psu/-/tags/v1.0.3
[1.0.2]: https://gitlab.com/psuapp/psu/-/tags/v1.0.2
[1.0.1]: https://gitlab.com/psuapp/psu/-/tags/v1.0.1
[1.0.0]: https://gitlab.com/psuapp/psu/-/tags/v1.0.0

View File

@ -66,7 +66,8 @@ For detailed instructions, see [How to use](#how-to-use) section.
Published Docker images are [tagged](https://hub.docker.com/r/psuapp/psu/tags) matching [GitLab tags](https://gitlab.com/psuapp/psu/-/tags):
- `dev` -> [`dev`](https://gitlab.com/psuapp/psu/-/tags/dev)
- `1`, `1.0`, `1.0.2`, `latest` -> [`v1.0.2`](https://gitlab.com/psuapp/psu/-/tags/v1.0.2)
- `1`, `1.0`, `1.0.3`, `latest` -> [`v1.0.3`](https://gitlab.com/psuapp/psu/-/tags/v1.0.3)
- `1`, `1.0`, `1.0.2` -> [`v1.0.2`](https://gitlab.com/psuapp/psu/-/tags/v1.0.2)
- `1`, `1.0`, `1.0.1` -> [`v1.0.1`](https://gitlab.com/psuapp/psu/-/tags/v1.0.1)
- `1`, `1.0`, `1.0.0` -> [`v1.0.0`](https://gitlab.com/psuapp/psu/-/tags/v1.0.0)
- `0.1.2` -> [`v0.1.2`](https://gitlab.com/psuapp/psu/-/tags/v0.1.2)
@ -78,13 +79,13 @@ Published Docker images are [tagged](https://hub.docker.com/r/psuapp/psu/tags) m
The `core` variant doesn't include `docker-compose`, so it's a bit smaller.
But you can't lint Docker compose/stack file before deploying a stack.
- `dev-core` -> [`dev`](https://gitlab.com/psuapp/psu/-/tags/dev)
- `1-core`, `1.0-core`, `1.0.2-core`, `core` -> [`v1.0.2`](https://gitlab.com/psuapp/psu/-/tags/v1.0.2)
- `1-core`, `1.0-core`, `1.0.3-core`, `core` -> [`v1.0.3`](https://gitlab.com/psuapp/psu/-/tags/v1.0.3)
The `debian` and `debian-core` variants use [Debian](https://www.debian.org) instead of [Alpine](https://alpinelinux.org/) as base image for `psu`.
- `dev-debian` -> [`dev`](https://gitlab.com/psuapp/psu/-/tags/dev)
- `dev-debian-core` -> [`dev`](https://gitlab.com/psuapp/psu/-/tags/dev)
- `1-debian`, `1.0-debian`, `1.0.2-debian`, `debian` -> [`v1.0.2`](https://gitlab.com/psuapp/psu/-/tags/v1.0.2)
- `1-debian-core`, `1.0-debian-core`, `1.0.2-debian-core`, `debian-core` -> [`v1.0.2`](https://gitlab.com/psuapp/psu/-/tags/v1.0.2)
- `1-debian`, `1.0-debian`, `1.0.3-debian`, `debian` -> [`v1.0.3`](https://gitlab.com/psuapp/psu/-/tags/v1.0.3)
- `1-debian-core`, `1.0-debian-core`, `1.0.3-debian-core`, `debian-core` -> [`v1.0.3`](https://gitlab.com/psuapp/psu/-/tags/v1.0.3)
#### Testing/debugging:
@ -94,7 +95,7 @@ For testing/debugging, you can use this Docker image in interactive mode, to run
docker run -v $(pwd)/docker-compose.yml:/docker-compose.yml -it --rm --entrypoint bash psuapp/psu
# Run any commands here! E.g.
$ psu --version
Portainer Stack Utils, version 1.0.2
Portainer Stack Utils, version 1.0.3
License GPLv3: GNU GPL version 3
```

View File

@ -729,5 +729,5 @@ The `psu` definition of a job is a Swarm [service](https://docs.docker.com/engin
Using a job is useful when you want to have a service who run a script (e.g. database migration).
And shutdown this service when its script is successfully executed.
See the service named `job` in the [`docker-stack-web-app.yml`](https://gitlab.com/psuapp/psu/tree/v1.0.2/tests/dockerfiles/docker-stack-web-app.yml) file, for a real use case.
See the service named `job` in the [`docker-stack-web-app.yml`](https://gitlab.com/psuapp/psu/tree/v1.0.3/tests/dockerfiles/docker-stack-web-app.yml) file, for a real use case.
It has both a container's label `job-name` and a restart policy set to `none`.

2
psu
View File

@ -27,7 +27,7 @@ set -e
# None #
############################
main() {
VERSION="1.0.2"
VERSION="1.0.3"
OPTIONS_TABLE=(
# option_key;flag_text;option_text;description