* refactor: rename deprecatedService to retiredService
- Updated all instances of deprecatedService to retiredService in service implementations, tests, and documentation.
- Changed attribute names from isDeprecated to isRetired in relevant schemas and service definitions.
- Adjusted tests and documentation to reflect the new terminology and ensure consistency.
* docs: rename deprecating-badges.md to retiring-badges.md
* refactor: rename files deprecated-service to retired-service
* refactor: update terminology from deprecated to retired in badge documentation
* change deprecated badge messages to 'retired badge'
- reduce confusion over deprecated badge source (badge, shields, endpoint service, user's service)
- reduce length of message to reduce traffic
update all deprecated services and base class code in a follow-up commit after discussion.
see https://github.com/badges/shields/pull/11792#issuecomment-4229267483
* update default deprecation message to 'retired badge'
* update deprecated badge messages to 'retired badge' in tests
* add not-planned and duplicate to issue state to [GithubIssueDetail]
Fixes GitHub issues/PRs - Support the "not planned" state
Fixes#11662
* fix: replace underscore with space in state reason response transformation
* fix: tests after not_planed replaced by not planned
* fix: update issue state color key from not_planned to not planned
* improve testing, forever closed
Co-authored-by: Pierre-Yves Bigourdan <10694593+PyvesB@users.noreply.github.com>
* remove redundent condition
---------
Co-authored-by: Pierre-Yves Bigourdan <10694593+PyvesB@users.noreply.github.com>
`created_at` refers to the creation time of the tag which the release points to, while `published_at` refers to the release publish time itself.
In cases where the same (old) tag is reused across multiple publishes, when using `created_at` the badge will show an outdated date, while `published_at` would show the correct release publish date.
* Add issueUrl parameter to deprecatedService helper
* refactor test response for GithubWorkflowStatus into a const
* Update variable name
---------
Co-authored-by: jNullj <15849761+jNullj@users.noreply.github.com>
* update pub-popularity deprecation label
updated docs now require deprecated service labels to show service name.
Fixes#11368
* update GithubWorkflowStatus deprecation label
comply with new doc requirement for deprecatoin label showing service name.
Fixes deprecation label compliance with updated docs
Fixes#11368
* fix: update message for Locked version of VCS dependency badge to use version validation
* revert to VCS deps
picked `https://github.com/ykdojo/editdojo/` as it seems to be real world example of somewhat popular repo with a VCS deps that is not often updated
* fix label
fix from prev commit
* add renderSizeBadge helper, use it everywhere
- switch from pretty-bytes to byte-size
- add renderSizeBadge() helper function
- match upstream conventions for metric/IEC units
- add new test helpers and use them in service tests
* unrelated: fix npm unpacked size query param schema
not strictly related to this PR
but I noticed it was broken
* chromewebstore: reformat size string, test against isIecFileSize
* add and consistently use parseDate and renderDateBadge helpers
also move
- age
- formatDate
- formatRelativeDate
to date.js
* fix bug in wordpress last update badge
* validate in formatDate() and age()
it is going to be unlikely we'll invoke either of these
directly now, but lets calidate here too
* remove unusued imports
* reverse colours for galaxy toolshed
* feat: add forcePrerelease option to renderVersionBadge function
Sometimes API would indicate if a version is pre-release while the version number does not have to be semantically a prerelease like in github-release service.
We don't use a isPrerelease that can also force a non-preleases as we trust here developer semantic over API tagging.
* refactor: GithubRelease to use renderVersionBadge
* refactor: GithubTag use renderVersionBadge
* refactor: change forcePrerelease to isPrerelease
* fix failing test 'Locked version of VCS dependency'
replaced tested package which is missing with another example
* Add regex validator for commit hash format
* fix vcs dependency test to use pipenv's pypiserver
* [GithubGoMod] Ignore comment after version (fixes#10079)
* add unit tests for GithubGoModGoVersion.transform
---------
Co-authored-by: chris48s <git@chris-shaw.dev>
* Support file path for GitHub last commit
* Support file path for GitLab last commit
* Support file path for Gitea last commit
* Define common `relativeUri` validator
* Sort imports
* Add more tests for path variations
* Fix test name
Co-authored-by: chris48s <chris48s@users.noreply.github.com>
* Update Gitea 404 message
* Handle case when no commits are returned for GitHub and GitLab
---------
Co-authored-by: chris48s <chris48s@users.noreply.github.com>
* update packages
* add plugin to strip autolinks in code blocks
* fix all the documentation for MDXv3
* remove check-docusaurus-versions
in docusaurus 3 this is now a hard error, not just a warning
* port upstream change to Curl component
fixes performing the 'execute' action when pressing enter
* init GithubCreatedAt service
* render raw created_at
* impl formatted date
* add color
* add test for absent repo
* add `reversed` parameter to `age` color formatter
* inverse the colors of the badge
---------
Co-authored-by: Studio <studio@192.168.1.20>