mirror of
https://github.com/J3vb/OwnCord.git
synced 2026-09-03 03:50:00 +03:00
J3vbandClaude Opus 5
4e7e4b12ac
Bumps the client version across every pin verify-versions enforces (package.json, tauri.conf.json, Cargo.toml) plus the two lockfiles that carry it, and the user-facing build examples in README.md, docs/deployment.md, docs/quick-start.md, docs/api.md and the issue-form placeholders. Deliberately NOT bumped: the v1.2.0-alpha.3 references in ci.yml, release.yml and docker-smoke.sh, which record the release that published from a red commit and are the reason the gate-evidence job exists; and the string in scripts/check-doc-counts.mjs, which is a selftest fixture asserting a version number is not read as a ledger claim. Rewriting either would falsify a record. CHANGELOG's Unreleased section becomes v1.2.0-alpha.4. Verified rather than assumed: - npm ci exits 0, so package-lock.json still matches package.json. - cargo metadata --locked exits 0, so Cargo.lock needs no regeneration. - The verify-versions comparison was run locally against tag v1.2.0-alpha.4: all three sources agree, so the tag will not be rejected. - npm run check passes end to end, exit 0. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
170 lines
4.7 KiB
YAML
170 lines
4.7 KiB
YAML
# A YAML issue form, not a Markdown template: only this format can mark a field
|
|
# required, so the environment detail a maintainer needs to reproduce a bug
|
|
# arrives with the report instead of after a round trip.
|
|
#
|
|
# Nothing in this repository validates this file's schema — prettier checks it
|
|
# parses as YAML and actionlint does not read it. A form that is valid YAML but
|
|
# an invalid issue form silently stops appearing in the chooser, so changes here
|
|
# want a look at the live "New issue" page afterwards.
|
|
name: Bug report
|
|
description: Something in the server, desktop client, or admin panel is broken.
|
|
title: "bug: "
|
|
labels: ["bug"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
**Do not report security vulnerabilities here.** Use
|
|
[private security reporting](https://github.com/J3vb/OwnCord/security/advisories/new)
|
|
instead — a public issue discloses the problem before there is a fix.
|
|
|
|
Questions, ideas and feedback belong in
|
|
[Discussions](https://github.com/J3vb/OwnCord/discussions), not here.
|
|
|
|
- type: textarea
|
|
id: what-happened
|
|
attributes:
|
|
label: What happened
|
|
description: What went wrong, and what you expected instead.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: repro
|
|
attributes:
|
|
label: Steps to reproduce
|
|
description: Numbered steps from a known starting state. A bug nobody can reproduce cannot be fixed.
|
|
placeholder: |
|
|
1. Start the server with …
|
|
2. In the client, open …
|
|
3. …
|
|
validations:
|
|
required: true
|
|
|
|
- type: dropdown
|
|
id: component
|
|
attributes:
|
|
label: Component
|
|
options:
|
|
- Server
|
|
- Desktop client
|
|
- Admin panel
|
|
- Both server and client
|
|
- Not sure
|
|
validations:
|
|
required: true
|
|
|
|
- type: input
|
|
id: server-version
|
|
attributes:
|
|
label: Server version
|
|
description: >-
|
|
Admin panel → Updates, or the banner the server prints at startup. It is
|
|
deliberately not exposed on the unauthenticated /health endpoint, so
|
|
"unknown" is a fine answer if you are not the operator. A server built
|
|
from source reports "dev".
|
|
placeholder: "1.2.0-alpha.4 / dev / unknown"
|
|
validations:
|
|
required: false
|
|
|
|
- type: input
|
|
id: client-version
|
|
attributes:
|
|
label: Client version
|
|
description: Settings → Logs shows it. Leave blank for a server-only bug.
|
|
placeholder: "1.2.0-alpha.4"
|
|
validations:
|
|
required: false
|
|
|
|
- type: dropdown
|
|
id: os
|
|
attributes:
|
|
label: Operating system
|
|
options:
|
|
- Windows 10
|
|
- Windows 11
|
|
- Linux
|
|
- Other
|
|
validations:
|
|
required: true
|
|
|
|
- type: dropdown
|
|
id: arch
|
|
attributes:
|
|
label: CPU architecture
|
|
description: ARM64 currently applies to the Linux desktop client; there is no ARM64 server release yet.
|
|
options:
|
|
- x64
|
|
- ARM64 (aarch64)
|
|
- Not sure
|
|
validations:
|
|
required: true
|
|
|
|
- type: dropdown
|
|
id: deployment
|
|
attributes:
|
|
label: How is the server deployed
|
|
options:
|
|
- Prebuilt binary (Windows)
|
|
- Prebuilt binary (Linux)
|
|
- Built from source
|
|
- Docker / Compose
|
|
- Linux systemd service
|
|
- Windows service (NSSM or Task Scheduler)
|
|
- Not applicable — client-only bug
|
|
- Not sure
|
|
validations:
|
|
required: true
|
|
|
|
- type: dropdown
|
|
id: tls-mode
|
|
attributes:
|
|
label: TLS mode
|
|
description: The `tls.mode` setting in config.yaml.
|
|
options:
|
|
- self_signed
|
|
- acme
|
|
- manual
|
|
- "off"
|
|
- Not applicable / not sure
|
|
validations:
|
|
required: false
|
|
|
|
- type: dropdown
|
|
id: topology
|
|
attributes:
|
|
label: How do clients reach the server
|
|
options:
|
|
- Same machine or LAN, direct
|
|
- Port forwarding to a public IP
|
|
- Behind a reverse proxy
|
|
- Tailscale
|
|
- Not sure
|
|
validations:
|
|
required: false
|
|
|
|
- type: dropdown
|
|
id: webview
|
|
attributes:
|
|
label: Client webview
|
|
description: >-
|
|
The desktop client renders through the OS webview — WebView2 on Windows,
|
|
WebKitGTK on Linux — so rendering and networking bugs often depend on it.
|
|
Skip this for a server-only bug.
|
|
options:
|
|
- WebView2 (Windows)
|
|
- WebKitGTK (Linux)
|
|
- Not applicable / not sure
|
|
validations:
|
|
required: false
|
|
|
|
- type: textarea
|
|
id: logs
|
|
attributes:
|
|
label: Logs, screenshots, or anything else
|
|
description: >-
|
|
Server console output or Settings → Logs from the client. Redact tokens,
|
|
invite codes and anything else you would not post publicly.
|
|
validations:
|
|
required: false
|