chore: update documentation for .NET requirement and scripts

[berviantoleo]

Reason for this change

Update the .NET requirements in documentation, previously only upgrading the templates.

#32894

Description of changes

• Update documentation regarding the minimum .NET version

Describe any new or updated permissions being added

N/A

Description of how you validated changes

N/A

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[berviantoleo]

The current code build is using .NET 6.

[aws-cdk-automation]

This PR has been in the BUILD FAILING state for 3 weeks, and looks abandoned. Note that PRs with failing linting check or builds are not reviewed, please ensure your build is passing

To prevent automatic closure:

• Resume work on the PR
• OR request an exemption by adding a comment containing 'Exemption Request' with justification e.x "Exemption Request: "
• OR request clarification by adding a comment containing 'Clarification Request' with a question e.x "Clarification Request: "

This PR will automatically close in 14 days if no action is taken.

[berviantoleo]

Clarification Request:

The current template is generating .NET 8, however, the integration test uses .NET 6. I saw in jsii, seems we can't move to .NET 6 and/or 8 because it has some issues. Is it fine if those components have inconsistent versions?

[mrgrain]

Clarification Request:

The current template is generating .NET 8, however, the integration test uses .NET 6. I saw in jsii, seems we can't move to .NET 6 and/or 8 because it has some issues. Is it fine if those components have inconsistent versions?

Templates are a default. Requirements are, well, minimal requirements. I think it's fine for these to be inconsistent. But of course .NET 6 being EOL means it's a bit pointless to continue supporting. We can update the recommendation right now, but not the script before an update on the internal build runner.

[berviantoleo]

TODO

[mrgrain]

thank you!

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 0149ff2
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.