Skip to content

fix: correct copyright holder to byte5 GmbH#48

Merged
iret77 merged 1 commit into
mainfrom
fix/copyright-holder-byte5-gmbh
Jun 15, 2026
Merged

fix: correct copyright holder to byte5 GmbH#48
iret77 merged 1 commit into
mainfrom
fix/copyright-holder-byte5-gmbh

Conversation

@iret77

@iret77 iret77 commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

What & why

The copyright holder in the LICENSE and README named the brand/domain byte5.ai instead of the legal entity that owns the rights, byte5 GmbH. Corrected both:

  • LICENSE: Copyright (c) 2026 byte5.aiCopyright (c) 2026 byte5 GmbH
  • README.md license line: © 2026 byte5.ai© 2026 byte5 GmbH

Left unchanged: the byte5.ai website URL in the README author line (it's a link to the site, not a rights statement), and the SPEC.md author line, which already reads "byte5 GmbH".

Affected spec section(s)

LICENSE; README "License" section. No SPEC normative content.

Trust impact

None — legal-metadata correction only.

Note on the v0.3 release

The immutable v0.3 tag snapshot still carries the old byte5.ai string. Per RELEASING.md tags are not re-pushed; main is corrected here and the next release will carry the right holder. Say the word if you'd like a v0.3.1 patch re-release instead.

Checklist

  • One logical change, conventional PR title
  • Cited the affected file(s)
  • Stated the trust impact (or "none")
  • docs-check passes

The copyright holder named the brand/domain 'byte5.ai' rather than the
legal entity. Corrects the LICENSE copyright line and the README
license line to 'byte5 GmbH'. The byte5.ai website URL in the README
author line is left as-is (it is a link to the site, not a rights
holder); the SPEC.md author line already reads 'byte5 GmbH'.
@iret77 iret77 merged commit 358695f into main Jun 15, 2026
2 checks passed
@iret77 iret77 deleted the fix/copyright-holder-byte5-gmbh branch June 15, 2026 19:30
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.

1 participant