Skip to content

docs: add cwctl specific-version upgrade instructions and iterative upgrade note#562

Open
sojan-official wants to merge 1 commit intomainfrom
chore/add-upgrade-instructions-to-cwctl-documentation
Open

docs: add cwctl specific-version upgrade instructions and iterative upgrade note#562
sojan-official wants to merge 1 commit intomainfrom
chore/add-upgrade-instructions-to-cwctl-documentation

Conversation

@sojan-official
Copy link
Member

Motivation

  • Clarify how to use cwctl to upgrade to a specific Chatwoot git ref to make targeted upgrades easier and safer.
  • Warn users about common failure modes (local repository changes) and reduce risk by recommending iterative upgrades instead of jumping many releases at once.

Description

  • Added a new usage example to self-hosted/deployment/chatwoot-ctl.mdx showing sudo cwctl -U <VERSION> with an example (sudo cwctl -U v4.3.0).
  • Clarified the difference between -u/--upgrade (latest stable) and -U/--Upgrade (specific git ref), noted that -U is experimental, and documented that it performs git checkout <VERSION> followed by git pull under the hood in self-hosted/deployment/chatwoot-ctl.mdx.
  • Added a note to self-hosted/deployment/upgrade.mdx recommending iterative upgrades across intermediate versions (e.g., avoid upgrading directly from v4.1 to v4.10).
  • Cleaned up trailing whitespace/newline issues in the modified files.

Testing

  • Ran git diff --check to ensure no whitespace/patch issues and it passed.
  • Verified file changes with git status --short which showed the two intended modified files and no unexpected changes.

Codex Task

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 959093bb73

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

```

<Note>
`-u`/`--upgrade` upgrades to latest stable (`master`), while `-U`/`--Upgrade` upgrades to a specific git ref and is currently experimental. Upgrades can fail when your Chatwoot repo has local code changes, so keep production changes clean and take backups before upgrading. Under the hood, `-U` performs a `git checkout <VERSION>` followed by `git pull`.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Avoid plain git pull after checking out a version tag

The new guidance says -U performs git checkout <VERSION> followed by git pull, and the example uses v4.3.0 (a release tag). When <VERSION> is a tag, checkout puts the repo in detached HEAD, where git pull fails with You are not currently on a branch ... git pull <remote> <branch>, so users following this documented path can hit an upgrade failure in production unless they pass a tracked branch name instead of a version tag.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant