Skip to content

docs: update supported versions in SECURITY.md - #6117

Merged
PastaPastaPasta merged 1 commit into
dashpay:developfrom
kwvg:secdoc_v21
Jul 19, 2024
Merged

PastaPastaPasta merged 1 commit into
dashpay:developfrom
kwvg:secdoc_v21

Conversation

@kwvg

@kwvg kwvg commented Jul 16, 2024

Copy link
Copy Markdown
Collaborator

Additional Information

Updates the supported versions list in SECURITY.md

Checklist:

  • I have performed a self-review of my own code (note: N/A)
  • I have commented my code, particularly in hard-to-understand areas (note: N/A)
  • I have added or updated relevant unit/integration/functional/e2e tests (note: N/A)
  • I have made corresponding changes to the documentation
  • I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

@kwvg kwvg added this to the 21.1 milestone Jul 16, 2024
@kwvg
kwvg requested review from PastaPastaPasta, UdjinM6 and knst July 16, 2024 14:38
@kwvg
kwvg marked this pull request as ready for review July 16, 2024 14:38
@kwvg kwvg changed the title docs: update SECURITY.md supported versions docs: update supported versions in SECURITY.md Jul 16, 2024

@PastaPastaPasta PastaPastaPasta left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK 878bce0

@UdjinM6 UdjinM6 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK 878bce0

@knst knst left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK 878bce0

@PastaPastaPasta
PastaPastaPasta merged commit bf0df81 into dashpay:develop Jul 19, 2024
@PastaPastaPasta PastaPastaPasta mentioned this pull request Jul 23, 2024
14 of 55 tasks
PastaPastaPasta added a commit to PastaPastaPasta/dash that referenced this pull request Jul 23, 2024
878bce0 docs: update SECURITY.md supported versions (Kittywhiskers Van Gogh)

Pull request description:

  ## Additional Information

  Updates the supported versions list in `SECURITY.md`

  ## Checklist:

  - [x] I have performed a self-review of my own code **(note: N/A)**
  - [x] I have commented my code, particularly in hard-to-understand areas **(note: N/A)**
  - [x] I have added or updated relevant unit/integration/functional/e2e tests **(note: N/A)**
  - [x] I have made corresponding changes to the documentation
  - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_

ACKs for top commit:
  PastaPastaPasta:
    utACK 878bce0
  UdjinM6:
    utACK 878bce0
  knst:
    utACK 878bce0

Tree-SHA512: d941a3ca0792b2f08f68cab562a35d869d8e93f627918a25a9753955b6103d1515899b0ca50ff936c966b9f9fd603e12d27b03267361c8f1030a31f9fffdf2ae
@UdjinM6 UdjinM6 modified the milestones: 21.1, 21 Jul 24, 2024
PastaPastaPasta added a commit that referenced this pull request Jul 25, 2024
cd0a3a6 Merge #6154: chore: remove trailing whitespaces in release notes (pasta)
6bc60a7 Merge #6151: chore: update seeds for v21 release (pasta)
88e949a Merge #6146: chore: bump assumevalid, minchainwork, checkpoints, chaintxdata (pasta)
cc14427 Merge #6144: docs: release notes for v21.0.0 (pasta)
0a8ece1 Merge #6122: chore: translations 2024-07 (pasta)
146d244 Merge #6140: feat: harden all sporks on mainnet to current values (pasta)
024d272 Merge #6126: feat: enable EHF activation of MN_RR on mainnet (pasta)
e780b3d Merge #6125: docs: update manpages for 21.0 (pasta)
5ede23c Merge #6118: docs: add release notes notifying change of default branch to `develop` (pasta)
1b6fe9c Merge #6117: docs: update supported versions in SECURITY.md (pasta)
27d20be Merge #6116: fix: mitigate crashes associated with some upgradetohd edge cases (pasta)

Pull request description:

  ## Issue being fixed or feature implemented
  Backports to v21 for rc.3; there are more PRs to be back ported here

  ## What was done?
  see commits

  ## How Has This Been Tested?

  ## Breaking Changes
  None

  ## Checklist:
    _Go over all the following points, and put an `x` in all the boxes that apply._
  - [x] I have performed a self-review of my own code
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have added or updated relevant unit/integration/functional/e2e tests
  - [x] I have made corresponding changes to the documentation
  - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_

ACKs for top commit:
  UdjinM6:
    utACK cd0a3a6

Tree-SHA512: 0a8d027c5952fcb61317cc413a0de1f3152ae675c5690942400c3e4655cc6a803c702a7e1b18d8dac77aa0f483783f5cdbe29d6c0592165c4f0517d6f37b91a4
PastaPastaPasta added a commit that referenced this pull request Jul 29, 2024
98a3393 chore: set release to true (pasta)
cd0a3a6 Merge #6154: chore: remove trailing whitespaces in release notes (pasta)
6bc60a7 Merge #6151: chore: update seeds for v21 release (pasta)
88e949a Merge #6146: chore: bump assumevalid, minchainwork, checkpoints, chaintxdata (pasta)
cc14427 Merge #6144: docs: release notes for v21.0.0 (pasta)
0a8ece1 Merge #6122: chore: translations 2024-07 (pasta)
146d244 Merge #6140: feat: harden all sporks on mainnet to current values (pasta)
024d272 Merge #6126: feat: enable EHF activation of MN_RR on mainnet (pasta)
e780b3d Merge #6125: docs: update manpages for 21.0 (pasta)
5ede23c Merge #6118: docs: add release notes notifying change of default branch to `develop` (pasta)
1b6fe9c Merge #6117: docs: update supported versions in SECURITY.md (pasta)
27d20be Merge #6116: fix: mitigate crashes associated with some upgradetohd edge cases (pasta)
db82817 Merge #6106: feat: create new composite quorum-command platformsign (pasta)
a45e6df Merge #6104: fix: adjust incorrect parameter description that says there is a default that doesn't exist (pasta)
7330982 Merge #6100: feat: make whitelist works with composite commands for platform needs (pasta)
9998ffd Merge #6096: feat: split type of error in submitchainlock - return enum in CL verifying code (pasta)
cdf7a25 Merge #6095: fix: createwallet to require 'load_on_startup' for descriptor wallets (pasta)
c1c2c55 Merge #6092: fix: mixing for partially unlocked descriptor wallets (pasta)
1175486 Merge #6073: feat: add logging for RPC HTTP requests: command, user, http-code, time of running (pasta)

Pull request description:

  ## Issue being fixed or feature implemented
  Suppressed changes from be83865 so the diff is empty.

  ## What was done?

  ## How Has This Been Tested?

  ## Breaking Changes

  ## Checklist:
  - [x] I have performed a self-review of my own code
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have added or updated relevant unit/integration/functional/e2e tests
  - [ ] I have made corresponding changes to the documentation
  - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_

ACKs for top commit:
  PastaPastaPasta:
    ACK 158cf86; no diff
  knst:
    ACK 158cf86

Tree-SHA512: 3310a39fbcb45bdf09f885fe77ba769c0a715869a3bb287eaf0f2cf54b35a7e1f832c88df3bd31097eabf2d375515c1b87ff05e0c3282cef642833a154c42bbe
PastaPastaPasta added a commit that referenced this pull request Oct 29, 2026
…d and flatpak for v24.0.0

b8f10bc chore: update translation source strings for v24.0.0 (pasta)
97460f6 doc: regenerate man pages for v24.0.0 (pasta)
cf37991 chore: add v24.0.0 release entry to flatpak metainfo (pasta)
000ccc6 docs: update supported versions in SECURITY.md for v24 (pasta)

Pull request description:

  ## Issue being fixed or feature implemented

  For v24.0.0, several per-release files need updating, on develop first and then on `v24.0.x` by backport (#7972). The pattern follows the man page PRs #6928 and #7140 and the SECURITY.md PRs #6117, #6461 and #6552:
  - develop's man pages still describe v23.1.9;
  - `SECURITY.md` lists only 23.x as supported;
  - the flatpak metainfo has no 24.0.0 entry;
  - the translation source strings were last refreshed in February 2026, before the shared-masternode GUI and the other v24 Qt work. Translators haven't seen those strings.

  ## What was done?

  - `SECURITY.md`: added 24.x as supported. 23.x stays supported.
  - Flatpak metainfo: added a `24.0.0` entry with an estimated release date of 2026-11-05, above the existing `23.1.9` entry.
  - `doc/man/*.1`: v24.0.0 man pages. develop's man pages describe the latest release, as the v23.0.0 and v23.1.0 pages did when #6928 and #7140 put them on develop. These pages were generated with `contrib/devtools/gen-manpages.py` from a v24.0.0 build of the release branch, with `CLIENT_VERSION_IS_RELEASE` set temporarily and not committed. Every page reads `v24.0.0`, with no rc, git hash or `-dirty` suffix.
  - Translations: ran `make -C src translate` on develop to refresh `src/qt/dashstrings.cpp`, `src/qt/locale/dash_en.ts` and `src/qt/locale/dash_en.xlf`. `dash_en.ts` goes from 1652 to 2718 source entries, mostly from the shared-masternode GUI. Once this is merged, Transifex picks up the new strings. Pulling translated `.ts` files is a separate step that needs Transifex access.

  Backport note: in #7972 the translation source files are generated from `v24.0.x` itself, not cherry-picked. develop has a few strings that the release branch doesn't, so `v24.0.x`'s `dash_en.ts` has 2706 entries. The other files are the same on both branches.

  ## How Has This Been Tested?

  - Checked that every `doc/man/*.1` reads `v24.0.0` and contains no `-rc`, `-dirty` or git hash.
  - Built develop with Qt from depends to run `make -C src translate`.
  - `test/lint/lint-whitespace.py` and `test/lint/lint-files.py` pass.
  - `git diff upstream/develop --stat` touches only the 11 files listed above.

  ## Breaking Changes

  None.

  ## Checklist:
  - [x] I have performed a self-review of my own code
  - [x] I have made corresponding changes to the documentation
  - [ ] I have assigned this pull request to a milestone

  🤖 Generated with [Claude Code](https://claude.com/claude-code)

Top commit has no ACKs.

Tree-SHA512: eb2f424ee2f5bb5968bc41cf7102cf845d4192d1345a620aec4498bafdfb7fbef6b2b9e0aca46b2dcf0338d4a47b409553c1ed3423ddfde54a30ea67519da3d2
PastaPastaPasta added a commit to PastaPastaPasta/dash that referenced this pull request Oct 29, 2026
…URITY.md and flatpak for v24.0.0

b8f10bc chore: update translation source strings for v24.0.0 (pasta)
97460f6 doc: regenerate man pages for v24.0.0 (pasta)
cf37991 chore: add v24.0.0 release entry to flatpak metainfo (pasta)
000ccc6 docs: update supported versions in SECURITY.md for v24 (pasta)

Pull request description:

  ## Issue being fixed or feature implemented

  For v24.0.0, several per-release files need updating, on develop first and then on `v24.0.x` by backport (dashpay#7972). The pattern follows the man page PRs dashpay#6928 and dashpay#7140 and the SECURITY.md PRs dashpay#6117, dashpay#6461 and dashpay#6552:
  - develop's man pages still describe v23.1.9;
  - `SECURITY.md` lists only 23.x as supported;
  - the flatpak metainfo has no 24.0.0 entry;
  - the translation source strings were last refreshed in February 2026, before the shared-masternode GUI and the other v24 Qt work. Translators haven't seen those strings.

  ## What was done?

  - `SECURITY.md`: added 24.x as supported. 23.x stays supported.
  - Flatpak metainfo: added a `24.0.0` entry with an estimated release date of 2026-11-05, above the existing `23.1.9` entry.
  - `doc/man/*.1`: v24.0.0 man pages. develop's man pages describe the latest release, as the v23.0.0 and v23.1.0 pages did when dashpay#6928 and dashpay#7140 put them on develop. These pages were generated with `contrib/devtools/gen-manpages.py` from a v24.0.0 build of the release branch, with `CLIENT_VERSION_IS_RELEASE` set temporarily and not committed. Every page reads `v24.0.0`, with no rc, git hash or `-dirty` suffix.
  - Translations: ran `make -C src translate` on develop to refresh `src/qt/dashstrings.cpp`, `src/qt/locale/dash_en.ts` and `src/qt/locale/dash_en.xlf`. `dash_en.ts` goes from 1652 to 2718 source entries, mostly from the shared-masternode GUI. Once this is merged, Transifex picks up the new strings. Pulling translated `.ts` files is a separate step that needs Transifex access.

  Backport note: in dashpay#7972 the translation source files are generated from `v24.0.x` itself, not cherry-picked. develop has a few strings that the release branch doesn't, so `v24.0.x`'s `dash_en.ts` has 2706 entries. The other files are the same on both branches.

  ## How Has This Been Tested?

  - Checked that every `doc/man/*.1` reads `v24.0.0` and contains no `-rc`, `-dirty` or git hash.
  - Built develop with Qt from depends to run `make -C src translate`.
  - `test/lint/lint-whitespace.py` and `test/lint/lint-files.py` pass.
  - `git diff upstream/develop --stat` touches only the 11 files listed above.

  ## Breaking Changes

  None.

  ## Checklist:
  - [x] I have performed a self-review of my own code
  - [x] I have made corresponding changes to the documentation
  - [ ] I have assigned this pull request to a milestone

  🤖 Generated with [Claude Code](https://claude.com/claude-code)

Top commit has no ACKs.

Tree-SHA512: eb2f424ee2f5bb5968bc41cf7102cf845d4192d1345a620aec4498bafdfb7fbef6b2b9e0aca46b2dcf0338d4a47b409553c1ed3423ddfde54a30ea67519da3d2
(cherry picked from commit 79a220f)
PastaPastaPasta added a commit that referenced this pull request Oct 29, 2026
…Y.md and flatpak for v24.0.0 (#7974)

80f6cbe chore: add the v23.1.9 release entry to flatpak metainfo (pasta)
5ba801f chore: use translation source strings generated from v24.0.x (pasta)
a3b9e30 Merge #7974: chore: update man pages, translation strings, SECURITY.md and flatpak for v24.0.0 (pasta)

Pull request description:

  ## Issue being fixed or feature implemented

  Backport of #7974 (develop, merged as 79a220f) to `v24.0.x`. It follows the usual develop-first pattern: #6928 and #7140 for man pages, #6117, #6461 and #6552 for SECURITY.md.

  Commits:
  1. `git cherry-pick -m1 -x 79a220f`. The man pages and `SECURITY.md` are identical to develop. The conflicts only came from this branch's different base files: man pages take #7974's version, and the flatpak metainfo gets #7974's `24.0.0` entry.
  2. `chore: use translation source strings generated from v24.0.x`. #7974's `dash_en.ts`, `dashstrings.cpp` and `dash_en.xlf` were generated on develop and contain a few develop-only strings. This commit replaces them with the output of `make -C src translate` on this branch: 2706 `dash_en.ts` source entries, against 2718 on develop.
  3. `chore: add the v23.1.9 release entry to flatpak metainfo`. develop already has this entry; adding it here keeps merging back clean.

  ## What was done?

  - `SECURITY.md`: added 24.x as supported (23.x stays supported).
  - Flatpak metainfo: added a `24.0.0` entry with an estimated release date of 2026-11-05. Also added the `23.1.9` entry that develop already has, so merging back stays clean.
  - `doc/man/*.1`: regenerated with `contrib/devtools/gen-manpages.py`. They were built with `CLIENT_VERSION_IS_RELEASE` temporarily set (not committed) so that the pages read `v24.0.0` and not an rc/git-describe string, the same as the v23.0.0 pages.
  - Translations: `make -C src translate` refreshed `dashstrings.cpp`, `dash_en.ts` and `dash_en.xlf`. That adds 1159 source strings (mostly the shared-masternode GUI) and removes 105 obsolete ones. Once this merges, Transifex picks up the new strings. Pulling translated `.ts` files has to be done separately, by someone with Transifex access.

  `configure.ac` is left alone: `CLIENT_VERSION_IS_RELEASE` stays `false` so rc.5 takes its version from the tag. Flipping it is the only change the final v24.0.0 tag needs on top of rc.5.

  ## How Has This Been Tested?

  - Built the branch against depends (with Qt). Checked that no `.1` file contains `-rc`, `-dirty` or a git hash.
  - `test/lint/lint-whitespace.py` and `test/lint/lint-files.py` pass.
  - `git diff upstream/v24.0.x --stat` only shows the 11 files listed above.

  ## Breaking Changes

  None.

  ## Checklist:
  - [x] I have performed a self-review of my own code
  - [x] I have made corresponding changes to the documentation
  - [ ] I have assigned this pull request to a milestone

  🤖 Generated with [Claude Code](https://claude.com/claude-code)

Top commit has no ACKs.

Tree-SHA512: 239d488fccccf52c9e6f3882bf82def94bc0b03eb122e9cd808e9b9a4da1935aec1ffd11c11569a11f03b8bcf12c598cdf610cafda63afce31ef75001b965465
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants