Skip to content

Ci/fork beta - #3337

Closed
PIKACHUIM wants to merge 12 commits into
OpenListTeam:mainfrom
PIKACHUIM:ci/fork-beta
Closed

PIKACHUIM wants to merge 12 commits into
OpenListTeam:mainfrom
PIKACHUIM:ci/fork-beta

Conversation

@PIKACHUIM

Copy link
Copy Markdown
Member

Summary / 摘要

  • This PR has breaking changes.
    / 此 PR 包含破坏性变更。
  • This PR changes public API, config, storage format, or migration behavior.
    / 此 PR 修改了公开 API、配置、存储格式或迁移行为。
  • This PR requires corresponding changes in related repositories.
    / 此 PR 需要关联仓库同步修改。

Related repository PRs / 关联仓库 PR:

  • OpenList-Frontend:
  • OpenList-Docs:

Related Issues / 关联 Issue

Testing / 测试

  • go test ./...
  • Manual test / 手动测试:

Checklist / 检查清单

  • I have read CONTRIBUTING.
    / 我已阅读 CONTRIBUTING。
  • I confirm this contribution follows the repository license, contribution policy, and code of conduct.
    / 我确认此贡献符合仓库许可证、贡献规范和行为准则。
  • I have formatted the changed code with gofmt, go fmt, or prettier where applicable.
    / 我已按适用情况使用 gofmt、go fmt 或 prettier 格式化变更代码。
  • I have requested review from relevant maintainers or code owners where applicable.
    / 我已在适用情况下请求相关维护者或代码所有者审查。

AI Disclosure / AI 使用声明

  • This PR includes AI-assisted content.
    / 此 PR 包含 AI 辅助内容。

Tools used / 使用工具:

  • ChatGPT
  • Codex
  • GitHub Copilot
  • Claude
  • Gemini
  • Other (please specify) / 其他(请注明):

Usage scope / 使用范围:

  • Code generation / 代码生成

  • Refactoring / 重构

  • Documentation / 文档

  • Tests / 测试

  • Translation / 翻译

  • Review assistance / 审查辅助

  • I have reviewed and validated all AI-assisted content included in this PR.
    / 我已审核并验证此 PR 中的所有 AI 辅助内容。

  • I have ensured that all AI-assisted commits include Co-Authored-By attribution.
    / 我已确保所有 AI 辅助提交都包含 Co-Authored-By 归属信息。

  • I can reproduce all AI-assisted content included in this PR without any AI tools.
    / 我可以在没有任何 AI 工具的情况下重现此 PR 中包含的所有 AI 辅助内容。

pikachuren and others added 12 commits October 16, 2026 18:00
- add `app` to `client_type` and emulate the Android App protocol stack (App client info, okhttp user agent, 10000023 channel, no web Caller)
- derive the client identity of the legacy personal cloud, family, group and route APIs from `client_type` instead of a hard coded ||9| x-DeviceInfo
- add `use_image_suffix_upload` to upload files as <name>.jpg and rename them back to <name> after the upload finishes
- report the App-only parallelUpload, storyVideoFile and userRegion fields in file/create when the App client is emulated
- match name conflicts on the final file name so the image suffix trick cannot delete a real x.jpg
- cover the new client helpers and the upload name wrapper with unit tests
- add the App protocol headers (Accept-Language, Content-Type, x-yun-url-type, x-yun-op-type, x-yun-sub-op-type) when the App client is emulated
- cover the added headers in the App header unit test
- Return an error when the uploaded object is not visible after retries.
- Keep existing-name replacement limited to a confirmed uploaded object.

Co-authored-by: LunelleEverdawn <lunelle+suyunmeng@oplist.org>
…OpenListTeam/OpenList into feat/139-app-client-image-suffix-upload
Provide SHA-256 midstates for App parallel upload parts so /file/create no longer rejects multipart uploads with 00010002.

When /file/create returns no file id, match the image suffix upload by name and size only, and refuse to rename if several candidates match instead of mistaking a leftover .jpg for this upload.
Build release binaries for linux/amd64, linux/arm64, windows/amd64 and darwin/amd64/arm64 on v* tags, publish archives to GitHub Releases, and push a multi-arch image to GitHub Container Registry.
…-upload

Feat/139 app client image suffix upload
ci: add fork release workflow for binaries and Docker image
Drop the tag trigger. Every push to main now builds the beta binaries, refreshes the rolling 'beta' prerelease assets, and pushes a multi-arch image tagged beta and sha-<short> to GitHub Container Registry.
Keep only the fork beta release pipeline so pushes and pull requests no longer trigger upstream build, release, docker, changelog, sync or labelling workflows.
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown

⚠️ PR 标题需以 feat(): , docs(): , fix(): , style(): , refactor(): , chore(): 其中之一开头,例如:feat(component): 新增功能。
⚠️ The PR title must start with feat(): , docs(): , fix(): , style(): , or refactor(): , chore(): . For example: feat(component): add new feature.

如果跨多个组件,请使用主要组件作为前缀,并在标题中枚举、描述中说明。
If it spans multiple components, use the main component as the prefix and enumerate in the title, describe in the body.

如果是破坏性变更,请在类型后添加 !,例如 feat(component)!: 破坏性变更。
For breaking changes, add ! after the type, e.g., feat(component)!: breaking change.

@PIKACHUIM PIKACHUIM closed this Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants