diff options
| author | 2025-06-06 15:14:37 +0200 | |
|---|---|---|
| committer | 2025-06-06 15:14:37 +0200 | |
| commit | 77eddea3aff27ffebf53d2341609221d4c1924e7 (patch) | |
| tree | 27ca0c930f93c12d2e36ea083c6dbf1eef8521b1 /vendor/code.superseriousbusiness.org/oauth2/v4/README.MD | |
| parent | [chore] blocklist -> allowlist config typo fix (#4242) (diff) | |
| download | gotosocial-77eddea3aff27ffebf53d2341609221d4c1924e7.tar.xz | |
[chore] updates code.superseriousbusiness.org/oauth2/v4 to ssb-v4.5.3-1 (#4245)
A brief note on the above change: Go does not seem to like version tagging outside of `v?[0-9\.]` formatting, so it translates `ssb-v4.5.3-1` to `v4.5.4-0.20250606121655-9d54ef189d42` and as such sees it as a "downgrade" compared to the previous `v4.9.0`. which functionally isn't a problem, everything still behaves as it should, but it means people can't just run `go get repo@latest` for this particular dependency.
Reviewed-on: https://codeberg.org/superseriousbusiness/gotosocial/pulls/4245
Co-authored-by: kim <grufwub@gmail.com>
Co-committed-by: kim <grufwub@gmail.com>
Diffstat (limited to 'vendor/code.superseriousbusiness.org/oauth2/v4/README.MD')
| -rw-r--r-- | vendor/code.superseriousbusiness.org/oauth2/v4/README.MD | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/vendor/code.superseriousbusiness.org/oauth2/v4/README.MD b/vendor/code.superseriousbusiness.org/oauth2/v4/README.MD new file mode 100644 index 000000000..b7145e2f9 --- /dev/null +++ b/vendor/code.superseriousbusiness.org/oauth2/v4/README.MD @@ -0,0 +1,9 @@ +# oauth2 + +Fork of https://github.com/go-oauth2/oauth2 + +You should probably use the original upstream library, this is largely for our own usecase in [GoToSocial](https://codeberg.org/superseriousbusiness/gotosocial), and provides zero compatibility guarantees between versions. + +Versioning is a little complex but attempts to follow upstream as `ssb-v4.5.3-x` where `ssb` = superseriousbusiness, `v4.5.3` is the upstream version, and `x` is our own revision starting at 1 for each fresh upstream release version. + +A copy of the upstream development branch can be found at `upstream-main`, and our main branch will (MUST!) be kept up-to-date with this with regular rebases.
\ No newline at end of file |
