Skip to content
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

chore(docs): align v6 docs with the next branch #10034

Merged
merged 11 commits into from
Feb 20, 2024
Merged

Conversation

jtoar
Copy link
Contributor

@jtoar jtoar commented Feb 19, 2024

This PR checks out the v6.x docs from the next branch and deletes the v6.0 docs on this branch. This is just standard procedure when we release a major. The next branch has the latest v6 docs (before it was v6.0 to v6.4, but they've been compressed to v6.x), while the main branch has the latest canary docs. Before we release a major and make a new next branch, we want the latest version of the v6 docs so that we can continue serving them under that tag on the docs site.

Most of the file changes are just moves because most docs received zero edits in minors 6.1 to 6.4.

This is accomplished via git checkout next -- docs/docs and then undoing some changes, especially those to files in docs/docs.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@jtoar jtoar added the release:chore This PR is a chore (means nothing for users) label Feb 19, 2024
@jtoar jtoar added this to the v7.0.0 milestone Feb 19, 2024
@jtoar jtoar added fixture-ok Override the test project fixture check changelog-ok labels Feb 19, 2024
@jtoar jtoar marked this pull request as draft February 19, 2024 23:15
@jtoar
Copy link
Contributor Author

jtoar commented Feb 19, 2024

This is normally a simple process but in scanning the diff there's some things that aren't right so I'll have to manually audit the files.

jtoar added a commit that referenced this pull request Feb 20, 2024
Last fix for v7 I noticed while trying to get
#10034 done. In talking to Josh
about his experiences deploying to Fly etc and some of the pain points
around that, I may introduce a `createServer` for the web side in a
minor. If they're in the same file (which they will be for now), parsing
argv with just port and host will be a problem. So to avoid that I've
made it so that it's apiPort and apiHost.
jtoar added a commit that referenced this pull request Feb 20, 2024
Last fix for v7 I noticed while trying to get
#10034 done. In talking to Josh
about his experiences deploying to Fly etc and some of the pain points
around that, I may introduce a `createServer` for the web side in a
minor. If they're in the same file (which they will be for now), parsing
argv with just port and host will be a problem. So to avoid that I've
made it so that it's apiPort and apiHost.
@jtoar jtoar marked this pull request as ready for review February 20, 2024 02:42
@jtoar jtoar merged commit 8b46768 into main Feb 20, 2024
40 checks passed
@jtoar jtoar deleted the ds-release/handle-docs-for-v7 branch February 20, 2024 02:48
jtoar added a commit that referenced this pull request Feb 20, 2024
This PR checks out the v6.x docs from the next branch and deletes the
v6.0 docs on this branch. This is just standard procedure when we
release a major. The next branch has the latest v6 docs (before it was
v6.0 to v6.4, but they've been compressed to v6.x), while the main
branch has the latest canary docs. Before we release a major and make a
new next branch, we want the latest version of the v6 docs so that we
can continue serving them under that tag on the docs site.

Most of the file changes are just moves because most docs received zero
edits in minors 6.1 to 6.4.

This is accomplished via `git checkout next -- docs/docs` and then
undoing some changes, especially those to files in `docs/docs`.
dac09 added a commit to dac09/redwood that referenced this pull request Feb 20, 2024
…sc-build

* 'feat/rsc-build' of github.com:dac09/redwood: (119 commits)
  chore(deps): update dependency @playwright/test to v1.41.2 (redwoodjs#10040)
  chore(crwa): update version in e2e test (redwoodjs#10037)
  chore(ci): update yarn.lock for changelog action (redwoodjs#10039)
  chore: bump TSTyche (redwoodjs#10036)
  chore(changelog): add v7 (redwoodjs#10038)
  v7.0.0
  Version docs to 7.0
  chore(docs): align v6 docs with the next branch (redwoodjs#10034)
  chore(docs): align v6 docs with the next branch (redwoodjs#10034)
  fix(server): prefix port/host with api, fix logging (redwoodjs#10035)
  fix(server): prefix port/host with api, fix logging (redwoodjs#10035)
  docs: Removes warning within Mailer documentation about Studio being experimental (redwoodjs#10033)
  docs: Within describeScenario documentation, change optimisation to use American English (redwoodjs#10032)
  docs(metadata): Fix spelling/typos (redwoodjs#10027)
  chore(release): link to previous releases and upgrade guides in the changelog (redwoodjs#10026)
  chore(ci): add changelog check to ci (redwoodjs#9989)
  fix(realtime): update logic for including sseLink (redwoodjs#10025)
  chore(k6 tests): update entry point (redwoodjs#10024)
  feat(server): add docs on the server file (redwoodjs#10019)
  fix(types): Fix TS type in createServer.test.ts (redwoodjs#10023)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixture-ok Override the test project fixture check release:chore This PR is a chore (means nothing for users)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant