Skip to content
This repository has been archived by the owner on Dec 30, 2022. It is now read-only.

fix: add notice for required content-type header on update tokens #252

Merged
merged 2 commits into from
Dec 2, 2022

Conversation

koalaty-code
Copy link
Contributor

@koalaty-code koalaty-code commented Dec 2, 2022

Description

  • Clearly document the required Content-Type header for PATCH /tokens/

Testing required outside of automated testing?

  • Not Applicable

Screenshots (if appropriate):

image

Rollback / Rollforward Procedure

  • Roll Forward
  • Roll Back

Reviewer Checklist

  • Description of Change
  • Description of outside testing if applicable.
  • Description of Roll Forward / Backward Procedure
  • Documentation updated for Change

@koalaty-code koalaty-code requested a review from a team as a code owner December 2, 2022 19:52
@djejaquino
Copy link
Contributor

Should point to the RFC in the disclaimer

@koalaty-code
Copy link
Contributor Author

Should point to the RFC in the disclaimer

@djejaquino added!

@koalaty-code koalaty-code merged commit a928de0 into master Dec 2, 2022
@koalaty-code koalaty-code deleted the patch-tokens-content-type branch December 2, 2022 20:16
bt-platform-eng pushed a commit that referenced this pull request Dec 2, 2022
## [1.76.2](v1.76.1...v1.76.2) (2022-12-02)

### Bug Fixes

* add notice for required content-type header on update tokens ([#252](#252)) ([a928de0](a928de0))
@bt-platform-eng
Copy link

🎉 This PR is included in version 1.76.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants