The `main` branch doesn't match the latest tag, leading to possible problems if you follow the upgrade guide for release

langgenius / dify

Dify is an open-source LLM app development platform. Dify's intuitive interface combines AI workflow, RAG pipeline, agent capabilities, model management, observability features and more, letting you quickly go from prototype to production.

https://dify.ai

Other

46.22k stars 6.52k forks source link

The `main` branch doesn't match the latest tag, leading to possible problems if you follow the upgrade guide for release #8660

Closed nadirvishun closed 2 hours ago

nadirvishun commented 2 hours ago

Self Checks

[X] I have searched for existing issues search for existing issues, including closed ones.
[X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
[X] Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

example the the release v0.8.3 upgrade guid:

git checkout main
git pull origin main

but the main branch doesn't match v0.8.3 tag, the code chagne v0.8.3 is 3 days ago, but main is 4 hours ago, If I pull the main branch, it doesn't actually necessarily match version 0.8.3.

2. Additional context or comments

Nope

3. Can you help us with this feature?

[ ] I am interested in contributing to this feature.

dosubot[bot] commented 2 hours ago

The main branch in the Dify repository is typically updated with new features and changes that have been tested in the deploy/dev branch before being merged into main ^[1]. This means that the main branch may not always match the latest tagged release, such as v0.8.3.

To ensure you are using the correct version for the upgrade, you should check out the specific tag instead of the main branch. For example, you can use the following commands:

git fetch --all --tags
git checkout tags/v0.8.3

This will ensure that you are using the exact code corresponding to the v0.8.3 release.

To continue talking to Dosu, mention @dosu.

crazywoola commented 2 hours ago

When you are trying to upgrade to the latest version, keep in mind, you should switch to that tag instead of using the main branch.

nadirvishun commented 2 hours ago

@crazywoola Maybe you can change the upgrade guide description in the release, it was always assumed that the main branch was the same as the latest tag branch:

crazywoola commented 2 hours ago

Thanks for the suggestion, we will do it later. @laipz8200