Release new version of protocol server

[emmayank]

Description

After completing the testing of the new changes in the protocol server, proceed with releasing a new version. This involves merging the changes from the develop branch into the master branch and creating a detailed release note with a proper changelog outlining all the changes and improvements.

Goals

• Ensure that all changes have been fully tested and approved.
• Merge the changes from the develop branch into the master branch to release the new version.
• Create a detailed release note, including a changelog of all the new features, updates, and bug fixes.
• Ensure the release note is clear and provides a summary of key improvements and important updates.

Expected Outcome

• A new version of the protocol server is successfully released with the changes from the develop branch.
• A comprehensive release note and changelog are created, documenting all updates, including OAS 3.1 validation, health check URL, HMAC authorization, Redis cache security, and other improvements.

Acceptance Criteria

• The changes are successfully merged from develop to master without any conflicts or issues.
• A detailed release note with a changelog is created and made available to stakeholders.
• The release is deployed, and all changes are live and functioning correctly.
• Post-release testing is conducted to ensure the changes are successfully deployed in production.

Mockups / Wireframes

NA

Product Name

Protocol Server

Domain

Server and Security

Tech Skills Needed

• Git Version Control (Merging Branches)
• Release Management
• Documentation and Changelog Creation
• Post-Release Testing

Complexity

Medium

Category

Release Management

Sub Category

Versioning and Release

Project View

Protocol Server

Project Name

Protocol Server