clean-up docs to avoid version-mismatches in BE and FE in new installs (for stable) #378
No reviewers
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#378
Loading…
Reference in a new issue
No description provided.
Delete branch ":stable"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I know its kinda bad form to want to merge into a stable branch, but since I only touched the docs really I hope this is okay?
I fixed up the documentation a little bit so it should take care that both BE and FE are installed in their correct and matching versions from the respective development-branches, when akkoma is installed from source using git.
This should avoid problems with new installations from git running develop-BE, but running but running Pleroma-FE in stable, which might result in some issues when upgrading and a breaking change is made in develop-BE that is not yet accounted for in stable-FE.
I rebased the docs on the develop-brach, so there are a few more changes to the stable branch, which come from develop-docs.
since we do need to fix this on stable like... asap, to prevent new users from running into the deprecated endpoint issue, i'll approve this
but yeah ideally we'll not merge into stable again any time soon