andromeda_cms 0.6.3-x86_64-linux → 0.7.1-x86_64-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 855263206dc24ebe87ce292d2bfd3c9c96d7927ae23eafed8ddb8e7c39cbf601
-  data.tar.gz: d1b5dbd227c3406c9f27495be1d11147c4a29b172f05694870494aad5b8aff83
+  metadata.gz: 37217a20b76903b85f456a94435176aa64ac1600c2f49ca3aec06a60ba8f144d
+  data.tar.gz: cee807e8a431423e015539343ad854b66b2aeb1749cf568f86c1d325f958a537
 SHA512:
-  metadata.gz: a81f2ac3c3404fab70619a1b010c2e6819c341b0c04aa29dbc65a4a7ad419129b4a1b28f412947d95747d7ae3973f5859efd830ea7018307281006aa6fe9bb2c
-  data.tar.gz: c172675fb835d11c25e5e597fbe7bccd21d7c488ffb214b6386ed38c5e36d53b7a70772a8e005d627fbb5c8140fbb905b27d37c081f6a4538da1ab2f1df9006a
+  metadata.gz: 9a3da1f52eaf5144a1e2de3291ca735bc22e3b855597283e87a3cae65bb93cb3848bf8df61342ab581bbabefcb29b135d2dfdb5b3cf9d25ff65b71b355efda98
+  data.tar.gz: 8466f36a95cdcd695bfe780b413dd0cbb4d5b6d7beffd102730af22e3dc79d6985abb340451349136dae61e1d347b05e3e8dbfb5967c35216beea5017b8cb4e6

data/CHANGELOG.md

@@ -5,6 +5,39 @@ All notable changes to this project are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.7.1] - 2026-11-08
+
+### Changed
+
+- The gem no longer restricts `json` to `< 3`, so applications can use
+  json 3. The bound worked around Rails 8.1 failing to decrypt session
+  cookies under json 3, which no longer happens: with json 3.1.0 the test
+  suite passes on Rails 8.0.5.1 and 8.1.4.1, and session cookies are
+  written and read back correctly on Rails 8.1.4.1.
+
+### Removed
+
+- The README's Troubleshooting entry, which recommended pinning `json` to
+  2.x, is gone.
+
+## [0.7.0] - 2026-10-16
+
+### Changed
+
+- YAML frontmatter is now read the way Astro 7.3.6 and later read it. Astro
+  replaced js-yaml with the `yaml` package (core schema, timestamps, merge
+  keys), and Andromeda follows. Plain scalars that only YAML 1.1 or Psych
+  treat as numbers are now strings, as they are in Astro: values with
+  underscores (`1_000`, `0x1_F`), the `0b` prefix, and signed hexadecimal
+  or octal (`-0x1F`). Numbers in the core schema are unchanged, including
+  `010` (10), `0o17`, `0x1F` and `1e3`.
+- A mapping that repeats a key now raises `Andromeda::SyntaxError` at the
+  second key, with its line and column, as Astro does. It used to keep the
+  last value silently. Keys are compared after resolution, so `1` and `01`
+  collide while `1` and `"1"` do not; repeated `<<` merge keys are allowed.
+  Content that repeats a key will fail to build until the duplicate is
+  removed.
+
 ## [0.6.3] - 2026-10-16
 
 ### Fixed
@@ -208,6 +241,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Generators: `andromeda:install`, `andromeda:collection`,
   `andromeda:component` and `andromeda:import_astro`.
 
+[0.7.1]: https://github.com/AndromedaCMS/andromeda_cms/releases/tag/v0.7.1
+[0.7.0]: https://github.com/AndromedaCMS/andromeda_cms/releases/tag/v0.7.0
 [0.6.3]: https://github.com/AndromedaCMS/andromeda_cms/releases/tag/v0.6.3
 [0.6.2]: https://github.com/AndromedaCMS/andromeda_cms/releases/tag/v0.6.2
 [0.6.1]: https://github.com/AndromedaCMS/andromeda_cms/releases/tag/v0.6.1

data/README.md

@@ -304,20 +304,6 @@ bundle exec rake     # compiles the Rust extension, then runs the tests
 bundle exec rake test:corpus  # after test/fetch_corpus.sh: parse ~370 real Astro files
 ```
 
-## Troubleshooting
-
-**`ArgumentError: wrong number of arguments (given 2, expected 1)` from `JSON.parse`.**
-Not this gem's code: Rails 8.1 calls `JSON.parse` with a positional options hash,
-which version 3 of the `json` gem no longer accepts, and decrypting a session
-cookie hits that path, so pages fail only once a session exists. The gem
-restricts `json` to `< 3` to avoid this. If you are on an older andromeda_cms,
-pin it in your own `Gemfile` until Rails ships a fix:
-
-```ruby
-# Gemfile
-gem "json", "~> 2.9"
-```
-
 ## Testing
 
 To run model tests against entries that are not files under `app/content`,

data/lib/andromeda/frontmatter.rb

@@ -25,45 +25,53 @@ module Andromeda
     # a non-blank line is seen, no `---`/`+++` after it is a fence.
     LEADING_RE = /\A\uFEFF?(?:[ \t]*\r?\n)*/
 
-    # Psych resolves plain scalars by YAML 1.1 rules; js-yaml, which Astro
-    # uses, follows YAML 1.2's core schema. The two disagree on values that
-    # really do appear in hand-written frontmatter, and a silent disagreement
-    # is worse than an error: `time: 12:30` becoming the integer 45000 passes
-    # every schema check and then displays nonsense. Each rule below mirrors
-    # what js-yaml 4 does with the same plain scalar.
+    # Psych resolves plain scalars by YAML 1.1 rules; Astro 7.3.6 and later
+    # read frontmatter with the `yaml` package (core schema, `timestamp` tag,
+    # merge keys), which follows YAML 1.2's core schema. The two disagree on
+    # values that really do appear in hand-written frontmatter, and a silent
+    # disagreement is worse than an error: `time: 12:30` becoming the integer
+    # 45000 passes every schema check and then displays nonsense. Each rule
+    # below mirrors what that parser does with the same plain scalar.
     class ScalarScanner < Psych::ScalarScanner
       # 1.1-only booleans; 1.2 keeps them as strings.
       YAML_1_1_ONLY_BOOL = /\A(?:[Yy]es|YES|[Nn]o|NO|[Oo]n|ON|[Oo]ff|OFF|[Yy]|[Nn])\z/
       # 1.1 base-60 (`1:30`) and comma-grouped (`1,000`) numbers; 1.2 has
       # neither, so these stay strings.
       YAML_1_1_ONLY_NUMBER = /\A[-+]?[0-9][0-9_]*(?:(?::[0-5]?[0-9])+|(?:,[0-9_]+)+)(?:\.[0-9_]*)?\z/
-      # 1.1 reads a leading zero as octal (`010` is 8); 1.2 reads it as decimal.
-      LEADING_ZERO_DECIMAL = /\A[-+]?0[0-9_]+\z/
-      # 1.2's explicit octal prefix, unknown to Psych.
-      OCTAL = /\A[-+]?0o[0-7_]+\z/
-      # 1.2 accepts an exponent without a decimal point (`1e3`); Psych does not.
-      EXPONENT_FLOAT = /\A[-+]?(?:[0-9][0-9_]*(?:\.[0-9_]*)?|\.[0-9_]+)[eE][-+]?[0-9]+\z/
+      # The core schema's integers. A leading zero is plain decimal (`010` is
+      # 10, where 1.1 reads octal); `0o` octal and `0x` hex take no sign.
+      INTEGER = /\A[-+]?[0-9]+\z/
+      OCTAL = /\A0o[0-7]+\z/
+      HEX = /\A0x[0-9a-fA-F]+\z/
+      # The core schema's floats, including an exponent without a decimal
+      # point (`1e3`), which Psych rejects. `.inf`/`.nan` are left to Psych.
+      FLOAT = /\A[-+]?(?:\.[0-9]+|[0-9]+(?:\.[0-9]*)?)(?:[eE][-+]?[0-9]+)?\z/
+      # Number-like spellings Psych accepts but the core schema does not
+      # (`1_000`, `0b1010`, `-0x1F`, `0o1_7`); they stay strings.
+      NON_CORE_NUMBER = /\A[-+]?(?:0[xXbBoO][0-9a-fA-F_]+|(?:[0-9][0-9_]*(?:\.[0-9_]*)?|\.[0-9_]+)(?:[eE][-+]?[0-9_]+)?)\z/
 
       def tokenize(string)
         case string
         when YAML_1_1_ONLY_BOOL, YAML_1_1_ONLY_NUMBER then string
-        when LEADING_ZERO_DECIMAL then Integer(string.delete("_"), 10)
-        when OCTAL then Integer(string.delete("_"))
-        when EXPONENT_FLOAT then Float(normalize_float(string.delete("_")))
+        when INTEGER then Integer(string, 10)
+        when OCTAL then Integer(string[2..], 8)
+        when HEX then Integer(string, 16)
+        when FLOAT then Float(normalize_float(string))
+        when NON_CORE_NUMBER then string
         else super
         end
       end
 
       private
 
-      # Ruby's Float() rejects the `1.e3` and `.5e3` spellings YAML allows.
+      # Ruby's Float() rejects the `1.`, `1.e3` and `.5e3` spellings YAML allows.
       def normalize_float(string)
-        string.sub(/\.(?=[eE])/, ".0").sub(/\A([-+]?)\./, "\\10.")
+        string.sub(/\.(?=[eE]|\z)/, ".0").sub(/\A([-+]?)\./, "\\10.")
       end
     end
 
-    # Restricts `!!` tags to Date/Time (matching js-yaml's default schema,
-    # which also has no notion of arbitrary Ruby classes) while still
+    # Restricts `!!` tags to Date/Time (matching the `yaml` package's core
+    # schema, which also has no notion of arbitrary Ruby classes) while still
     # permitting the two classes plain `YYYY-MM-DD`/timestamp scalars resolve
     # to, so unquoted dates round-trip instead of raising
     # Psych::DisallowedClass.
@@ -76,7 +84,7 @@ module Andromeda
     end
 
     # Plain (non-"safe") visitor so anchors/aliases resolve instead of
-    # raising -- js-yaml allows them by default, and copied Astro content may
+    # raising -- the `yaml` package resolves them by default, and copied Astro content may
     # rely on them.
     class ToRuby < Psych::Visitors::ToRuby
       def initialize
@@ -199,6 +207,8 @@ module Andromeda
       return {} if node.nil?
 
       reject_alias_explosion!(node, path: path, content_start_line: content_start_line)
+      reject_duplicate_keys!(node, ScalarScanner.new(ClassLoader.new), path: path,
+                                   content_start_line: content_start_line)
       ToRuby.new.accept(node) || {}
     rescue Psych::SyntaxError => e
       # Psych's own #line/#column are 0-based and relative to `text` (the
@@ -305,6 +315,36 @@ module Andromeda
     end
     private_class_method :expanded_size
 
+    # Astro's `yaml` parser reports a repeated mapping key as an error, where
+    # Psych silently keeps the last value. Keys are compared after resolution,
+    # so `1` and `01` collide while `1` and `"1"` do not. Plain `<<` merge
+    # keys, alias keys and collection keys are left out.
+    def reject_duplicate_keys!(node, scanner, path:, content_start_line:)
+      if node.is_a?(Psych::Nodes::Mapping)
+        seen = {}
+        node.children.each_slice(2) do |key, _value|
+          next unless key.is_a?(Psych::Nodes::Scalar)
+          next if key.plain && key.value == "<<"
+
+          resolved = key.plain ? scanner.tokenize(key.value) : key.value
+          resolved = resolved.to_f if resolved.is_a?(Numeric)
+          if seen.key?(resolved)
+            raise syntax_error("duplicate key #{key.value.inspect}", path: path,
+                                                                    content_start_line: content_start_line,
+                                                                    relative_line: key.start_line,
+                                                                    relative_column: key.start_column)
+          end
+
+          seen[resolved] = true
+        end
+      end
+
+      node.children.to_a.each do |child|
+        reject_duplicate_keys!(child, scanner, path: path, content_start_line: content_start_line)
+      end
+    end
+    private_class_method :reject_duplicate_keys!
+
     def syntax_error(message, path:, content_start_line:, relative_line:, relative_column:)
       Andromeda::SyntaxError.new(
         message,

data/lib/andromeda/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Andromeda
-  VERSION = "0.6.3"
+  VERSION = "0.7.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: andromeda_cms
 version: !ruby/object:Gem::Version
-  version: 0.6.3
+  version: 0.7.1
 platform: x86_64-linux
 authors:
 - LIMHAUS Inc.
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2026-10-16 00:00:00.000000000 Z
+date: 2026-11-07 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: railties
@@ -70,16 +70,16 @@ dependencies:
   name: json
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "<"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '3'
+        version: '0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "<"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '3'
+        version: '0'
 description: |
   Andromeda brings Astro's content collections to an ordinary Ruby on Rails
   app. Markdown and MDX files copied from an Astro project are validated