docs(home): update layer version to 62 for package version 2.33.1

[ericbn]

Issue number: #3780

Summary

Changes

Update layer version to 62 for package version 2.33.1. Not sure if this is an automatic process that was not triggered on the latest release, but the docs still mention the layer version 61 which has the package version 2.33.0 installed.

User experience

Users will have the correct reference to layer version 62 for when they want to use the latest 2.33.1 version of aws-lambda-powertools.

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[boring-cyborg]

Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need.
In the meantime, check out the #python channel on our Powertools for AWS Lambda Discord: Invite link

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[heitorlessa]

thank you so much @ericbn - something indeed happened with our automation. For the first time, it only updated parts of it.

cc @rubenfonseca

[heitorlessa]

issue created #3780 - discovered the root cause.. it was the new GitHub Action upload-artifact major version which had a race condition in the last release, which led to the collection of Layer ARN be partial hence the PR reflecting parts with 62 version only.

cc @dreamorosi @am29d @rubenfonseca @sthulb so you're aware of the risk for next release until we use dynamic artifact + merge.

[boring-cyborg]

Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience!

[heitorlessa]

Docs rebuilt with the new Layer version. Thank you so much again @ericbn 🫶

[dreamorosi]

Thanks for the heads up @heitorlessa! Just to make sure I understand the risk: was the issue only confined to the ARNs in the docs, or was the layer publishing also affected?

[heitorlessa]

Docs only. As layers were published, the JSON artefact upload partially at random. The docs update rely on that JSON

…

On Fri, 16 Feb 2024 at 10:09, Andrea Amorosi ***@***.***> wrote: Thanks for the heads up @heitorlessa <https://github.com/heitorlessa>! Just to make sure I understand the risk: was the issue only confined to the ARNs in the docs, or was the layer publishing also affected? — Reply to this email directly, view it on GitHub <#3778 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZPQBGFNC5CLXYCZS7PPR3YT4O45AVCNFSM6AAAAABDLC3SN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBYGAYDMNBXGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>