Skip to content

Commit 844c092

Browse files
committed
[ci skip] Fix major v1 version for amazon.
1 parent d3ca869 commit 844c092

File tree

5 files changed

+9
-9
lines changed

5 files changed

+9
-9
lines changed

CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
77

88
## Unreleased
99

10-
## [1.1.1] - 2023-05-20
10+
## [1.1.1] [1.1.2] - 2023-05-20
1111

1212
- Simple major version docker tags. Ex: 1
1313

Cargo.lock

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[package]
22
name = "crypteia"
3-
version = "1.1.1"
3+
version = "1.1.2"
44
edition = "2021"
55

66
[[bin]]

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ When building your own Lambda Containers, use both the `crypteia` binary and `li
8484
There are two options for Lambda containers. The easiest is to use Docker's multi stage builds with our [Extension Containers]([https://github.com/orgs/rails-lambda/packages?ecosystem=container&tab=packages&ecosystem=container&q=extension](https://github.com/orgs/rails-lambda/packages?repo_name=crypteia&q=extension)) to copy the `/opt` directory matching your platform and Crypteia version number. example below. Remember to use `-debian` vs `-amzn` if you are using your own Linux containers. Or change the version number depending on your needs.
8585

8686
```dockerfile
87-
FROM ghcr.io/rails-lambda/crypteia-extension-amzn:latest AS crypteia
87+
FROM ghcr.io/rails-lambda/crypteia-extension-amzn:1 AS crypteia
8888
FROM public.ecr.aws/lambda/nodejs:18
8989
COPY --from=crypteia /opt /opt
9090
ENV LD_PRELOAD=/opt/lib/libcrypteia.so
@@ -136,7 +136,7 @@ S3_BUCKET_NAME=my-bucket ./package/deploy
136136
If you are using Crypteia on your own Docker containers without the Lambda Extension mechanics, you can simply set the `ENTRYPOINT` to the Crypteia binary which fetches your environment variables so the shared object preload can use them.
137137

138138
```dockerfile
139-
FROM ghcr.io/rails-lambda/crypteia-extension-amzn:latest AS crypteia
139+
FROM ghcr.io/rails-lambda/crypteia-extension-amzn:1 AS crypteia
140140
FROM ubuntu
141141
COPY --from=crypteia /opt /opt
142142
ENV LD_PRELOAD=/opt/lib/libcrypteia.so

package/deploy-image-amzn

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -35,10 +35,10 @@ docker push "${BASE_NAME_ARM64}:${CRYPTEIA_VERSION}"
3535
docker push "${BASE_NAME_ARM64}:latest"
3636

3737
docker manifest create \
38-
"ghcr.io/rails-lambda/crypteia-extension-amzn:${CRYPTEIA_VERSION}" \
39-
--amend "${BASE_NAME_AMD64}:${CRYPTEIA_VERSION}" \
40-
--amend "${BASE_NAME_ARM64}:${CRYPTEIA_VERSION}"
41-
docker manifest push "ghcr.io/rails-lambda/crypteia-extension-amzn:${CRYPTEIA_VERSION}"
38+
"ghcr.io/rails-lambda/crypteia-extension-amzn:${CRYPTEIA_VERSION_MAJOR}" \
39+
--amend "${BASE_NAME_AMD64}:${CRYPTEIA_VERSION_MAJOR}" \
40+
--amend "${BASE_NAME_ARM64}:${CRYPTEIA_VERSION_MAJOR}"
41+
docker manifest push "ghcr.io/rails-lambda/crypteia-extension-amzn:${CRYPTEIA_VERSION_MAJOR}"
4242

4343
docker manifest create \
4444
"ghcr.io/rails-lambda/crypteia-extension-amzn:${CRYPTEIA_VERSION}" \

0 commit comments

Comments
 (0)