Update release tags for 1.3.17

[Divyaasm]

Description

Update release tags for 1.3.17

Issues Resolved

List any issues this PR will resolve, e.g. Closes [...].

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.29%. Comparing base (8816c60) to head (c4ed193).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4749      +/-   ##
==========================================
+ Coverage   92.04%   92.29%   +0.24%     
==========================================
  Files         193      193              
  Lines        6411     6411              
==========================================
+ Hits         5901     5917      +16     
+ Misses        510      494      -16     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[gaiksaya]

@prudhvigodithi @peterzhuamazon Do we not have automation for this yet?

[prudhvigodithi]

No @gaiksaya but we extend this workflow https://github.com/opensearch-project/opensearch-build/blob/main/jenkins/release-manifest-commit-lock/release-manifest-commit-lock.jenkinsfile having a new action for for final manifest tag update.

[gaiksaya]

No @gaiksaya but we extend this workflow https://github.com/opensearch-project/opensearch-build/blob/main/jenkins/release-manifest-commit-lock/release-manifest-commit-lock.jenkinsfile having a new action for for final manifest tag update.

I see! Do we have an issue for this? Looks like good enhancement. We can call that workflow after tag-creation workflow is finished.