Repository navigation
Promote 0.4.17 to QA - #64
Merged
Merged
Conversation
…erge on their own; log lines from requests stay on one line Dependabot covers the backend packages, the web app packages, the GitHub Actions and the base images, each weekly in a patch-and-minor group and a major group, with security fixes grouped as they come. The Dependency updates workflow labels each update, holds major ones for review, and takes automatic ones one at a time: up to date with dev, the next version and its changelog section (heading only, or a For admins line for a security fix in something Requestarr ships), build started on that commit, and auto-merge once it passes. Build's Changelog job checks a dispatched update's version against the branch it goes into. Text from a request (paths, user names, the webhook event type) is logged with its line breaks escaped, so it can't add a fake log entry. Version 0.4.3.
Dependency updates on dev: grouped, patch and minor merge on their own, majors held for review
…when fetch-metadata can't (version 0.4.4) Dependabot's newer grouped commit message has no versions in its metadata block, so fetch-metadata returns no update type and no group, and a patch security fix was held for review. The workflow now reads the "Updates X from A to B" lines and the "Bumps the G group" line itself in that case.
Dependency updates: read an update's size from its commit message when fetch-metadata can't
…version 0.4.5) The workflow's own push queued pull request runs that wait for an approval (action_required), and the update step counted them as a failed build and held #48 for review. Only the build it starts by dispatch counts now.
Dependency updates: only the dispatched build decides whether an update failed
…the NUnit version (version 0.4.6)
Dependency updates: merge as soon as build passes, one NUnit version, fast-uri security fix (version 0.4.6)
…t is signed and can merge without an extra approval (version 0.4.7)
…ge or hold, instead of relying on another run
Dependency updates: signed version commit, so an automatic update can merge on its own (version 0.4.7)
…n't know dev's newest commit yet (version 0.4.8)
Dependency updates: retry the API when dev has only just moved (version 0.4.8)
…pdates Bumps the frontend group with 7 updates in the / directory: | Package | From | To | | --- | --- | --- | | [@sentry/integrations](https://github.com/getsentry/sentry-javascript) | `7.119.1` | `7.120.4` | | [react-focus-lock](https://github.com/theKashey/react-focus-lock) | `2.9.4` | `2.13.7` | | [@types/lodash](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/lodash) | `4.17.26` | `4.17.27` | | [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) | `8.71.2` | `8.72.0` | | [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser) | `8.71.2` | `8.72.0` | | [core-js](https://github.com/zloirock/core-js/tree/HEAD/packages/core-js) | `3.50.0` | `3.51.0` | | [postcss](https://github.com/postcss/postcss) | `8.5.30` | `8.5.31` | Updates `@sentry/integrations` from 7.119.1 to 7.120.4 - [Release notes](https://github.com/getsentry/sentry-javascript/releases) - [Changelog](https://github.com/getsentry/sentry-javascript/blob/7.120.4/CHANGELOG.md) - [Commits](getsentry/sentry-javascript@7.119.1...7.120.4) Updates `react-focus-lock` from 2.9.4 to 2.13.7 - [Release notes](https://github.com/theKashey/react-focus-lock/releases) - [Changelog](https://github.com/theKashey/react-focus-lock/blob/master/CHANGELOG.md) - [Commits](theKashey/react-focus-lock@v2.9.4...v2.13.7) Updates `@types/lodash` from 4.17.26 to 4.17.27 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/lodash) Updates `@typescript-eslint/eslint-plugin` from 8.71.2 to 8.72.0 - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.72.0/packages/eslint-plugin) Updates `@typescript-eslint/parser` from 8.71.2 to 8.72.0 - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.72.0/packages/parser) Updates `core-js` from 3.50.0 to 3.51.0 - [Release notes](https://github.com/zloirock/core-js/releases) - [Changelog](https://github.com/zloirock/core-js/blob/master/CHANGELOG.md) - [Commits](https://github.com/zloirock/core-js/commits/v3.51.0/packages/core-js) Updates `postcss` from 8.5.30 to 8.5.31 - [Release notes](https://github.com/postcss/postcss/releases) - [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md) - [Commits](postcss/postcss@8.5.30...8.5.31) --- updated-dependencies: - dependency-name: "@sentry/integrations" dependency-version: 7.120.4 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: frontend - dependency-name: "@types/lodash" dependency-version: 4.17.27 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: frontend - dependency-name: "@typescript-eslint/eslint-plugin" dependency-version: 8.72.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: frontend - dependency-name: "@typescript-eslint/parser" dependency-version: 8.72.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: frontend - dependency-name: core-js dependency-version: 3.51.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: frontend - dependency-name: postcss dependency-version: 8.5.31 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: frontend - dependency-name: react-focus-lock dependency-version: 2.13.7 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: frontend ... Signed-off-by: dependabot[bot] <support@github.com>
…tend-d5f7e8194e Web app packages: Bump the frontend group across 1 directory with 7 updates
… and the running version on production's logo (version 0.4.10) - Dark icon sets (production, dev, QA, beta) replaced with the delivered files: the background is the header gray (#282828) instead of black. Light sets, the pinned-tab shape and the square logos are unchanged. - Header and sign-in logo: the delivered wide logos (branch bar beside a full-height R), chosen by environment and theme like the icons and sized by height. - Production's logo is drawn by Requestarr: a green bar with the running version beside the delivered R, using the branch labels' rules and Inter Display Black outlines (.github/version_logo_glyphs.py), never cached, so it always matches the version running.
Dark icons on the header gray, full-height header logo, and the running version on production's logo (0.4.10)
…the page shows through (version 0.4.11) - Light icon sets replaced with the delivered charcoal-arrow files; dark favicons and header logos replaced with the delivered transparent ones. Favicons and header logos are transparent behind the R; the phone icons, tiles and logo.png keep their solid backgrounds. - New light-purple header logos for the light theme's purple header (beta's bar is white there); the sign-in page keeps the light set. - The production version logo has no background either, and is drawn for the purple header too.
Charcoal arrow, a logo for the purple light header, and logos the page shows through (0.4.11)
…0.4.12) - On start, the bot sets the built-in Requestarr picture and the environment's banner (teal, dev, QA, beta) only where they differ, in one change. It remembers Discord's id for what it set, so a picture changed by hand is left alone; takeOver lets Requestarr's always win. Discord refusals are logged and retried on a later start. - botProfile.keepUpToDate and botProfile.takeOver in provisioning, stored as settings; the test stacks take over their hand-uploaded pictures and can start with it off (REQUESTARR_BOT_PROFILE=false). - Setup guide 5.13.
…le stays valid for the QA stack's older version
The bot keeps its own Discord picture and banner up to date (0.4.12)
…logo on the loading screen (version 0.4.13) - The sign-in panel header is dark gray in both themes, so its logo (production's version logo too) is always the dark set's, with the light arrow; it no longer follows the theme switch. - The loading screen shows the header's logo for the environment and theme instead of the old purple placeholder, which is gone from the app.
Sign-in logo from the dark set, and the environment's logo on the loading screen (0.4.13)
…ersion 0.4.14) Test stacks on this PC: dev 39797, 38989, 37878 (was 19797, 28989, 27878); QA 29797, 28989, 27878 (was 9797, 18989, 17878). Beta's band 19797, 18989, 17878 is recommended in its settings template and setup guide; production and the image keep 9797, 8989, 7878. Containers keep their standard ports inside Docker, so webhooks and backend URLs are unchanged.
One port band per environment, counting down to the standard ports (0.4.14)
…k (version 0.4.15, work in progress)
… before staging (work in progress)
…sts; live check shows member visibility
…ug reports included
QA test checklist in Discord that gates staging, and bug reports that reach GitHub (0.4.15)
…fail items without the report limit, every test-server report reaches GitHub, checklist in its own group (version 0.4.16) - Passes deferred the press and then edited the card into plain text, which Discord refuses for a card (MESSAGE_CANNOT_REMOVE_COMPONENTS_V2_FLAG): every press answered "Something went wrong". The card shows the pass; the press needs no reply. The test responder now enforces Discord's rule. - Failing on a checklist item (admins only) and its form skip the members' report limit and don't count toward it. - Reports from the bug reports panel: the private menu becomes "Sending your report..." and is removed once the card is posted, so no private reply points at the panel after it moves. - Panels: a move posts the new one and removes the old one without editing it first; a panel already last is left alone (the bot's own new panel used to trigger an edit), so nothing is marked "edited" for nothing. - Bug reports: always filed on dev, QA and beta; the key also comes from REQUESTARR_GITHUB_ISSUES_TOKEN (dev and QA stacks, staging compose); the card says exactly why a report isn't filed (FilingProblem from GitHub's answer); unfiled reports are filed on every bot ready, once each, and their cards and checklist items follow. - The gate blocks on any report from the server not on GitHub, whatever its version, and names it; self-test in CI. - The checklist channel moves into an admin-only Requestarr QA group (migration 012: QaCategoryId, FilingProblem).
…restart marks nothing edited; live check: admin fails three items in a row past his own limit, channel order read back, its own cards removed
QA checklist fixes: Passes without errors, admins fail items past the report limit, every test-server report reaches GitHub, checklist in its own group (0.4.16)
…d by hand (version 0.4.17)
Test stacks: Requestarr's bot picture and banner win over one uploaded by hand (0.4.17)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves
qatodev@b4b3cb8(version 0.4.17): exactly these commits, nothing newer. Merged as a fast-forward ofqaonce the build check passes.Requested by: the owner: "promote to QA"
Versions now in QA
Commits