Repository navigation
Feature Matrix documentation - #104
Merged
Merged
Conversation
mpantel
pushed a commit
to mpantel/hyperstack
that referenced
this pull request
Sep 2, 2026
Feature Matrix documentation
mpantel
added a commit
to mpantel/hyperstack
that referenced
this pull request
Sep 2, 2026
…yperstack-org#104) hyperstack-org#44 applied PERMITTED_YAML_CLASSES only on Rails >= 7.1; below that the column fell back to a bare serialize :data. But Rails 6.1.7.x carries the same safe-load backport, so YAMLColumn#yaml_load there is already a restricted safe_load with nothing permitted on this column -- the payload dumps fine and raises on the way back in. hyperstack-org#44 fixed the dump side; this is the load side. Unreachable until now: per hyperstack-org#103 the hyperstack_queued_messages table was never created on Rails 6.1, so nothing was ever queued there and nothing read back. The two defects were nested -- fixing hyperstack-org#103 turned the path on, and this was underneath. Fix applies the same list through a coder on the column (Rails 6.1's serialize takes any object responding to dump/load) rather than widening config.active_record.yaml_column_permitted_classes, keeping hyperstack-org#44's principle. aliases: true because a payload can repeat a value and Psych emits an alias. Verified across two full-matrix passes (6854, 6856): 20/20 rails-hyperstack cell runs green. Adds queued_message_coder_spec.rb, including a guard-the-guard example that fails if Rails stops raising there. Closes hyperstack-org#104
mpantel
added a commit
to mpantel/hyperstack
that referenced
this pull request
Sep 2, 2026
hyper-operation: permit the queued-message classes on Rails 6.1 too (hyperstack-org#104) Closes hyperstack-org#103 and hyperstack-org#104 See merge request ru/hyperstack!143
mpantel
added a commit
to mpantel/hyperstack
that referenced
this pull request
Sep 2, 2026
…k-org#100, which landed after the bump commit
mpantel
added a commit
to mpantel/hyperstack
that referenced
this pull request
Sep 2, 2026
changelog: cover hyperstack-org#104, hyperstack-org#105 and hyperstack-org#100, which landed after the bump commit See merge request ru/hyperstack!147
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
2 participants
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.
Based on a short discussion in Gitter chat.
A table listing implemented, partially implemented, missing or bugged features.
Just so we can have some sort of overview what still needs work.
This is just an initial proposal, other people will have to add information. Also, the table columns can be changed.