Skip to content

Commit c0d4f4a

Browse files
committedJun 23, 2023
Merge branch 'release-1.26.160'
* release-1.26.160: Bumping version to 1.26.160 Add changelog entries from botocore chore: update ancient issue bot (#3734)
2 parents 0c110bd + 252234e commit c0d4f4a

File tree

6 files changed

+35
-11
lines changed

6 files changed

+35
-11
lines changed
 

‎.changes/1.26.160.json

+22
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
[
2+
{
3+
"category": "``devops-guru``",
4+
"description": "[``botocore``] This release adds support for encryption via customer managed keys.",
5+
"type": "api-change"
6+
},
7+
{
8+
"category": "``fsx``",
9+
"description": "[``botocore``] Update to Amazon FSx documentation.",
10+
"type": "api-change"
11+
},
12+
{
13+
"category": "``rds``",
14+
"description": "[``botocore``] Documentation improvements for create, describe, and modify DB clusters and DB instances.",
15+
"type": "api-change"
16+
},
17+
{
18+
"category": "``verifiedpermissions``",
19+
"description": "[``botocore``] Added improved descriptions and new code samples to SDK documentation.",
20+
"type": "api-change"
21+
}
22+
]

‎.github/workflows/stale_issue.yml

+1-8
Original file line numberDiff line numberDiff line change
@@ -14,15 +14,9 @@ jobs:
1414
runs-on: ubuntu-latest
1515
name: Stale issue job
1616
steps:
17-
- uses: aws-actions/stale-issue-cleanup@v4
17+
- uses: aws-actions/stale-issue-cleanup@v6
1818
with:
1919
issue-types: issues
20-
ancient-issue-message: Greetings! It looks like this issue hasn’t been active in longer
21-
than one year. We encourage you to check if this is still an issue in the latest release.
22-
In the absence of more information, we will be closing this issue soon.
23-
If you find that this is still a problem, please feel free to provide a comment or upvote
24-
with a reaction on the initial post to prevent automatic closure. If the issue is already closed,
25-
please feel free to open a new one.
2620
stale-issue-message: Greetings! It looks like this issue hasn’t been
2721
active in longer than five days. We encourage you to check if this is still an issue in the latest release.
2822
In the absence of more information, we will be closing this issue soon.
@@ -42,7 +36,6 @@ jobs:
4236
# Issue timing
4337
days-before-stale: 5
4438
days-before-close: 2
45-
days-before-ancient: 365
4639
# If you don't want to mark a issue as being ancient based on a
4740
# threshold of "upvotes", you can set this here. An "upvote" is
4841
# the total number of +1, heart, hooray, and rocket reactions

‎CHANGELOG.rst

+9
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,15 @@
22
CHANGELOG
33
=========
44

5+
1.26.160
6+
========
7+
8+
* api-change:``devops-guru``: [``botocore``] This release adds support for encryption via customer managed keys.
9+
* api-change:``fsx``: [``botocore``] Update to Amazon FSx documentation.
10+
* api-change:``rds``: [``botocore``] Documentation improvements for create, describe, and modify DB clusters and DB instances.
11+
* api-change:``verifiedpermissions``: [``botocore``] Added improved descriptions and new code samples to SDK documentation.
12+
13+
514
1.26.159
615
========
716

‎boto3/__init__.py

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@
1717
from boto3.session import Session
1818

1919
__author__ = 'Amazon Web Services'
20-
__version__ = '1.26.159'
20+
__version__ = '1.26.160'
2121

2222

2323
# The default Boto3 session; autoloaded when needed.

‎setup.cfg

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ universal = 0
33

44
[metadata]
55
requires_dist =
6-
botocore>=1.29.159,<1.30.0
6+
botocore>=1.29.160,<1.30.0
77
jmespath>=0.7.1,<2.0.0
88
s3transfer>=0.6.0,<0.7.0
99

‎setup.py

+1-1
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@
1313

1414

1515
requires = [
16-
'botocore>=1.29.159,<1.30.0',
16+
'botocore>=1.29.160,<1.30.0',
1717
'jmespath>=0.7.1,<2.0.0',
1818
's3transfer>=0.6.0,<0.7.0',
1919
]

0 commit comments

Comments
 (0)
Please sign in to comment.