Repository navigation
TINYDOC-3660: Serve the markdown and text files with a UTF-8 charset - #4394
Merged
Merged
Conversation
kemister85
requested review from
a team,
TheSpyder,
metricjs,
soritaheng,
tiny-ben-tran,
tiny-james and
tjdett
and removed request for
a team
October 13, 2026 07:07
kemister85
marked this pull request as ready for review
October 13, 2026 07:07
spocke
approved these changes
Oct 13, 2026
tiny-ben-tran
approved these changes
Oct 14, 2026
kimwoodfield
approved these changes
Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ticket: TINYDOC-3660
What was broken: S3 served
.mdand.txtfiles without a charset (content-type: text/markdown). Browsers then decoded the UTF-8 files as Windows-1252, so https://www.tiny.cloud/docs/sitemap.md showed—instead of—. This also affectedAGENTS.md, every pageindex.mdand thellms*.txtfiles.What is fixed:
.mdfiles are served astext/markdown; charset=utf-8and.txtfiles astext/plain; charset=utf-8. Cache-control and all other files are unchanged.How:
.github/workflows/deploy_docs_v2.ymlnow uploads*.mdand*.txtin their ownaws s3 synccalls with an explicit--content-type, because the sync's guessed type has no charset.Pre-checks:
feature/<version>/,hotfix/<version>/,staging/<version>/, orrelease/<version>/.Review: