Skip to content

Fastlane per-release changelogs are too long #12815

@IzzySoft

Description

@IzzySoft

Checklist

  • I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
  • I made sure that there are no existing issues - open or closed - which I could contribute my information to.
  • I have read the FAQ and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.

Affected version

n/a

Steps to reproduce the bug

From our monthly report:

  • build/org.schabi.newpipe/metadata/cs/changelogs/1005.txt has 622 chars
  • build/org.schabi.newpipe/metadata/fr/changelogs/1005.txt has 703 chars
  • build/org.schabi.newpipe/metadata/hi/changelogs/1005.txt has 596 chars
  • build/org.schabi.newpipe/metadata/hu/changelogs/1005.txt has 624 chars
  • build/org.schabi.newpipe/metadata/it/changelogs/1005.txt has 656 chars
  • build/org.schabi.newpipe/metadata/pa/changelogs/1005.txt has 603 chars
  • build/org.schabi.newpipe/metadata/sk/changelogs/1005.txt has 621 chars
  • build/org.schabi.newpipe/metadata/uk/changelogs/1005.txt has 650 chars

Expected behavior

all changelogs are within the 500 char limit according to the fastlane specs

Actual behavior

changelogs exceeding the limit

Screenshots/Screen recordings

No response

Logs

No response

Affected Android/Custom ROM version

No response

Affected device model

No response

Additional information

No response

Metadata

Metadata

Assignees

Labels

localisation/translationEverything that has to do with translations or Weblate

Type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions