Skip to content

docs(standard): remove misleading remark for softwareVersion - #288

Merged
bfabio merged 1 commit into
mainfrom
software-version
Feb 13, 2026
Merged

docs(standard): remove misleading remark for softwareVersion#288
bfabio merged 1 commit into
mainfrom
software-version

Conversation

@bfabio

Copy link
Copy Markdown
Contributor

Fix #270.

@vercel

vercelBot commented Jan 30, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

ProjectDeploymentActionsUpdated (UTC)
publiccode-ymlReadyReadyPreview, CommentJan 30, 2026 9:00am

@bfabio

Copy link
Copy Markdown
ContributorAuthor

@yaml-9000 patch

@yaml-9000

Copy link
Copy Markdown

Thanks for your contribution 🙏

This is now marked as a bugfix-change proposal to the standard,
this means that this change won't break any compatibility with the old versions of the Standard.

Example of bugfix changes are typo fixes.

The next eligible voting round will take place on May 30, 2026

cc @publiccodeyml/steering-committee

📄 Voting procedure | 📄 Working Group Charter | 🤖 bot commands

@yaml-9000yaml-9000 added standard-bugfix-change This change fixes a bug. There's no new features or changing existing ones vote-draft Change proposal to the Standard or to the governance procedures labels Jan 30, 2026
@bfabio

Copy link
Copy Markdown
ContributorAuthor

@yaml-9000 vote-start

@yaml-9000

Copy link
Copy Markdown

Voting is now open on this proposal!

If you are a member of the Steering Committee you can now vote!

The polls will stay open for 14 days, until Fri, 13 Feb 2026 09:03:33 GMT.

Leave a 👍 (thumbs up) on this comment to accept the proposal or a 👎 (thumbs down) to reject it.

cc @publiccodeyml/steering-committee

📄 Voting procedure | 📄 Working Group Charter | 🤖 bot commands

@bfabio

Copy link
Copy Markdown
ContributorAuthor

@yaml-9000 vote-end

@yaml-9000

Copy link
Copy Markdown

Vote results

The results of the vote are:

VoteMembersVotes countPercentage
👍 Approve@bzg@bfabio@tomootes3100.0%
👎 Reject0-

Proposal approved 👍

This proposal is now ready to be merged and get released with a new version of the standard.

cc @publiccodeyml/maintainers

Details

First round: unanimity required

The following users voted (includes non-members of the steering committee):

  • bzg voted 👍

  • bfabio voted 👍

  • tomootes voted 👍

📄 Voting procedure | 📄 Working Group Charter | 🤖 bot commands

@bfabio
bfabio merged commit 2a8fc10 into mainFeb 13, 2026
2 checks passed
@bfabio
bfabio deleted the software-version branch February 13, 2026 09:17
bfabio added a commit to publiccodeyml/bot that referenced this pull request Feb 15, 2026
Normalize the current date to 00:00 so the comparison is day based.
This should have said "Jan 30":
publiccodeyml/publiccode.yml#288 (comment)
bfabio added a commit to publiccodeyml/bot that referenced this pull request Feb 15, 2026
Normalize the current date to 00:00 so the comparison is day based.
This should have said "Jan 30":
publiccodeyml/publiccode.yml#288 (comment)
bfabio added a commit to publiccodeyml/bot that referenced this pull request Feb 15, 2026
Normalize the current date to 00:00 so the comparison is day based.
This should have said "Jan 30":
publiccodeyml/publiccode.yml#288 (comment)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

standard-bugfix-changeThis change fixes a bug. There's no new features or changing existing onesvote-approvedvote-draftChange proposal to the Standard or to the governance procedures

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@bfabio@yaml-9000