Use version 1.93.0 in RELEASES.md instead of 1.93

[tyilo]

No description provided.

[rustbot]

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[tyilo]

Seems like the id's of the following section links are also missing a .0 patch version, but I don't know if that should be changed:

$ rg 'a id="1\\.\\d{2}[^.]' RELEASES.md
...
419:<a id="1.90-Language"></a>
432:<a id="1.90-Compiler"></a>
447:<a id="1.90-Platform-Support"></a>
459:<a id="1.90-Libraries"></a>
471:<a id="1.90-Stabilized-APIs"></a>
510:<a id="1.90-Cargo"></a>
518:<a id="1.90-Rustdoc"></a>
526:<a id="1.90-Compatibility-Notes"></a>
1333:<a id="1.84-Rustdoc"></a>
1533:<a id="1.83-Rustdoc"></a>
1888:<a id="1.80-Language"></a>
1898:<a id="1.80-Compiler"></a>
1914:<a id="1.80-Libraries"></a>
1928:<a id="1.80-Stabilized-APIs"></a>
1996:<a id="1.80-Cargo"></a>
2007:<a id="1.80-Rustdoc"></a>
2016:<a id="1.80-Compatibility-Notes"></a>
2033:<a id="1.80-Internal-Changes"></a>

[cuviper]

The older ones can probably be updated too, but lets consider that separately and just worry about the current release now. Thanks for this!

@bors r+ rollup

[rust-bors]

📌 Commit 6b8432b has been approved by cuviper

It is now in the queue for this repository.

[weihanglo]

The older ones can probably be updated too, but lets consider that separately and just worry about the current release now. Thanks for this!

Probably a minor issue though wouldn't that break existing links to them?

[cuviper]

Probably a minor issue though wouldn't that break existing links to them?

Yes, if any exist at all. I'm fine with leaving the older releases alone.

[tyilo]

Would it make sense to add some CI job that checks that the minor version is always included? It seems like this has happened multiple times before.