Skip to content

Upgrade Cinc to version 18.4.12 #2713

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 14, 2024
Merged

Conversation

himani2411
Copy link
Contributor

Description of changes

  • Upgrade Cinc to version 18.4.12

Tested as part of Draft PR and using custom Cinc Installer Link #2692

Tests

  • Describe the automated and/or manual tests executed to validate the patch.
  • Describe the added/modified tests.

References

  • Link to impacted open issues.
  • Link to related PRs in other packages (i.e. cookbook, node).
  • Link to documentation useful to understand the changes.

Checklist

  • Make sure you are pointing to the right branch.
  • If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
  • Check all commits' messages are clear, describing what and why vs how.
  • Make sure to have added unit tests or integration tests to cover the new/modified code.
  • Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

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

@himani2411 himani2411 added the 3.x label Apr 22, 2024
@himani2411 himani2411 requested review from a team as code owners April 22, 2024 19:19
@himani2411 himani2411 force-pushed the develop branch 4 times, most recently from 23055f4 to 5f84b93 Compare May 9, 2024 16:20
@hanwen-pcluste hanwen-pcluste merged commit f37b065 into aws:develop May 14, 2024
30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants