chore: merge upstream to 1.27.3 for ENG-911 #16
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PR aws#1698 * fixpackaging: Add changelog entry Fix rebase error Special case pyrsistent
Also includes a workaround for python/mypy#9940.
PR aws#1704 * mypy-fixes: Add changelog entry Add additional missing types Upgrade mypy version
Bumps [py](https://github.com/pytest-dev/py) from 1.5.3 to 1.10.0. - [Release notes](https://github.com/pytest-dev/py/releases) - [Changelog](https://github.com/pytest-dev/py/blob/master/CHANGELOG.rst) - [Commits](pytest-dev/py@1.5.3...1.10.0) Signed-off-by: dependabot[bot] <[email protected]>
Bump py from 1.5.3 to 1.10.0
Fixed mypy type declarations for AuthResponse routes (should be a List)
Looking at definition of ApiGateway::BasePathMapping it looks only to be a string The previous code sets up a template reference to the RestAPI but from the definition of AWS::Serverless::Api, there is only a StageName property. Looking at the model for the WebSocket custom domain, I think we just need the name of the api state only.
Updates the requirements on [pip](https://github.com/pypa/pip) to permit the latest version. - [Release notes](https://github.com/pypa/pip/releases) - [Changelog](https://github.com/pypa/pip/blob/main/NEWS.rst) - [Commits](pypa/pip@9.0.0...21.1) Signed-off-by: dependabot[bot] <[email protected]>
…21.2 Update pip requirement from <21.1,>=9 to >=9,<21.2
PR aws#1712. * request-types: Fix type definitions for Request
This allows sqs handlers to be configured with the Chalice/CDK integration. Fixes aws#1681
Add example for testing POST views with json bodies
PR aws#1720 * queue-arn: Update API docs with new param Add changelog entry for queue_arn Add optional queue_arn to on_sqs_message
Due to Chalice using relative paths when importing an app, in Python 3.8.10, we'll use a cached version of a previous test case's sys.path location which will result in import errors, for example see: https://github.com/jamesls/chalice/runs/2529906754 The GitHub action for 3.8 upgraded from 3.8.9 to 3.8.10 which triggered this issue. It looks like this issue has been resolved upstream (https://bugs.python.org/issue44070) but we still need a fix in Chalice until a new version of 3.8 is released. Probably not a bad idea to clear the cache anyways if we're removing stuff from sys.path.
PEP 600 defines a new "perennial tag" for manylinux going forward. Projects such as numpy have started to use this new tag, which results in Chalice being unable to package numpy. We might be able to relax how he validate valid platform tags for Lambda, but for now we roughly follow what's outlined in the "Package Installers" section in the PEP. We'll map the old manylinux tag to the new format, parse out the glibc version, and then verify it's compatible with Lambda's glibc (based on a given runtime image). The other fix need was to support multiple compatibility tags (defined in PEP 425 "Compressed Tag Sets"), which numpy was also using: numpy-1.20.3-cp37-cp37m-manylinux_2_12_x86_64.manylinux2010_x86_64.whl
PR aws#1731. * fix-py38-tests: Update packager to support new manylinux tag Clear import cache in tests
Needed for the lambda waiters
We may need to explore doing batch waits in the create/update case so we don't block on each function.
PR aws#1732. * wait-active: Wait for function state to be active when deploying Bump botocore min version
PR aws#1958. * add-readme-python-version: Remove note about py27, no longer supported Add python3.9 to README
PR aws#1953 * update-aws-tf-provder-constraint: Add changelog entry for TF update Change AWS Terraform provider constraint to allow versions 4.x
This is taking a more conservative approach to these changes.
PR aws#1949 * cleanup-app-runtime: Revert several refactorings in app.py Various app runtime cleanups
Probot no longer works, so we need to switch over to GitHub actions. This uses the same actions as other repos in the aws org. I've disabled the ancient issues, as my immediate needs are to get parity with the old behavior, which was to close issuse that have no received a response. I've also set dry-run mode so I can have this run for a bit and verify the actions it would take make sense.
As of July 18, 2022 you can no longer creating new Lambda functions with Python 3.6 As of August 17, 2022 you can no longer update new Lambda functions with Python 3.6.
PR aws#1963. * py-versions: Remove 3.6 testing
PR aws#1960 * stale-issue: Switch stale issue closing to github actions
After several dry run outputs, it's performing the expected actions so we can enable this workflow.
PR aws#1964 * activate-stalecheck: Enable stale issue github action
This includes several code fixes to make the latest mypy/pylint happy as well as simplification to the requirements files. Our doc build script already installs the dev deps so we can simplify things and consolidate them all into a single requirements file.
PR aws#1968 * update-deps: Update dependencies to latest versions
PR aws#1969 * fix-schedule-type: Fix typedef for schedule decorator
PR aws#1970 * patch-1: Fix a typo
The regex needed to be updated to account for the type being added. Fixes aws#1971.
PR aws#1972 * fix-version-update: Fix version string updates
ghost
changed the title
ghost
self-assigned this
johnsca
approved these changes
Oct 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
merge upstream