ruby-brandur-json-schema (0.21.0-1) [PTS] [DDPO]

OK: VCS matches the version in the archive

Git: https://salsa.debian.org/ruby-team/ruby-brandur-json-schema.git
JSON
Enter a full Vcs-* header, supported schemes are: Vcs-Bzr, Vcs-Cvs, Vcs-Darcs, Vcs-Git, Vcs-Hg, Vcs-Mtn, Vcs-Svn.
For Vcs-Git append -b branch to select the branch name; append [subdir] if the debian/ directory is not in the repository root.
The next upload will reset the information from the source package headers.
Branch: debian/latest
Path: debian/changelog
Repo size: 323584
Browser: https://salsa.debian.org/ruby-team/ruby-brandur-json-schema
Last scan: 2025-11-25 00:37:09+00
Next scan: 2025-11-30 00:46:00+00
CI pipeline status: success

Debian changelog in Git:

ruby-brandur-json-schema (0.21.0-1) unstable; urgency=medium

  [ Utkarsh Gupta ]
  * Add salsa-ci.yml

  [ Debian Janitor ]
  * Bump debhelper from old 11 to 12.
  * Set debhelper-compat version in Build-Depends.
  * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
    Repository-Browse.
  * Apply multi-arch hints.
    + ruby-brandur-json-schema: Add :any qualifier for ruby dependency.
  * Update watch file format version to 4.
  * Bump debhelper from old 12 to 13.

  [ Simon Quigley ]
  * Team upload.
  * New upstream release.
  * Drop {XS,XB}-Ruby-Versions from control.
  * Use ${ruby:Depends} for runtime dependencies.
  * Update Standards-Version to 4.7.2, no changes needed.
  * Add validate_date_needs_timestamp.patch to correct timestamp test.

 -- Simon Quigley <tsimonq2@debian.org>  Sat, 01 Nov 2025 12:05:53 -0500

This branch is even with tag debian/0.21.0-1