Merged in bugfix/lambda-env (pull request #8)

Lambda Layer support
twentyfourg · May 27, 2021 · 093bf19 · 093bf19
2 parents cc8cafb + 7be6d25
commit 093bf19
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 6 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -8,4 +8,5 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [1.1.2] - 2021-05-27
 ### Changed
-- Updated the logic gate to determine if the code is running in a container or Lambda. It now uses `AWS_LAMBDA_FUNCTION_NAME` instead of `AWS_EXECUTION_ENV` since `AWS_LAMBDA_FUNCTION_NAME` isn't always set which caused issues when using this package in a Lambda layer.
+- Updated the logic gate to determine if the code is running in a container or Lambda. It now uses `AWS_LAMBDA_FUNCTION_NAME` instead of `AWS_EXECUTION_ENV` since `AWS_LAMBDA_FUNCTION_NAME` isn't always set which caused issues when using this package in a Lambda layer.
+- Updated pipeline only publish package. It no longers updates the patch number.
diff --git a/bitbucket-pipelines.yml b/bitbucket-pipelines.yml
@@ -8,9 +8,5 @@ pipelines:
           name: Deploying to npm.24g.dev
           image: node:12-alpine
           script:
-            - npm install 
             - npm run lint
-            - apk --update add git
-            - npm version patch -m "[skip ci] %s"
-            - npm publish --registry https://npm.24g.dev
-            - git push
+            - npm publish --registry https://npm.24g.dev