Repository navigation
Upgrade framework and version website assets - #18
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Implemented by Copilot (AI), on behalf of @dblock.
Upgrade slack-ruby-bot-server to 2.3.0 and rack-server-pages to 0.3.0 with narrow lockfile changes. Version all local page script/image URLs; render help and privacy through ERB without changing their public URLs or text. Apply the central framework server_pages configuration in the existing custom stack, setting private, no-cache for rendered pages while retaining default static content ETags and timestamp behavior. Preserve Slack installation, API routing, CORS, robots, commands, and RTM defaults.
Add request regressions for all three pages, conditional static responses, and a Firefox logo-reload check. Required RuboCop commands passed without new exclusions or relaxed thresholds; full suite: 61 examples, zero failures on Ruby 3.4.6. Browser validation used an isolated session-only port override so concurrent bot suites do not collide.
The original checkout and its ahead local master are untouched. Not merged or deployed.
Hosted RSpec and RuboCop checks both pass on
d00663b.