You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Conceivably, this could mean that someone had wanted
to test something this week but did not, because they
suspected the testing environment was not up-to-date.
The text was updated successfully, but these errors were encountered:
@ElectricNroff, this will be fixed in the next release for cve-services. There was a version numbering hotfix on prod during the last deploy. That is why it only exists on Dev and Prod.
We intend to do a deploy to test tomorrow, (Jan 8th) and that will resolve the numbering issues on a majority of these. With the remainder getting fixed at the end of January when it is finished going through the pipeline.
Currently https://cveawg-test.mitre.org/api-docs/ and
https://cveawg-adp-test.mitre.org/api-docs/ and
https://cveawg-prod-staging.mitre.org/api-docs/ and
https://cveawg-int.mitre.org/api-docs/
say CVE Services API 2.4.0 but
https://cveawg.mitre.org/api-docs/ and
https://cveawg-dev.mitre.org/api-docs/
say CVE Services API 2.5.0.
Conceivably, this could mean that someone had wanted
to test something this week but did not, because they
suspected the testing environment was not up-to-date.
The text was updated successfully, but these errors were encountered: