Checked this just now on a ubuntu instance, then a buster instance just to ensure the same environment and the install provided me with the latest version. Are you still experiencing this issue?
I could just be doing something stupid, but I’m hitting the exact problem described with 2.2.14 being offered by apt, but 2.2.18 being latest. Brand new Debian 11 install, and I was able to install vault, consul, and terraform from the hashicorp repo using apt commands. Vagrant however, as the OP notes, is not cooperating.
I’m not sure how to resolve it, any suggestions are appreciated - but it might be some kind of conflict with the debian OS repos?
$ apt info vagrant -a
Package: vagrant
Version: 2.2.14+dfsg-1
Priority: optional
Section: admin
Maintainer: Debian Ruby Team <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
With apt info vagrant -a it shows both the above described 2.2.14, and also offers 2.2.3 from the deb maintainers.
When I do the same lookup for terraform, the maintainer is HashiCorp <support@hashicorp.com>.
I don’t know enough about apt to understand how it determines what to offer, but maybe the extra string +dfsg-1 after the version is making apt think the 2.2.18 is an older version? Maybe the priority field?
Basically, HashiCorp is not prioritizing their packages higher than the the base package which comes with Ubuntu. So if you run apt-get install vagrant, the default will be the version that comes with the base OS repositories by default.
This is easy to correct, but AFAIK, HashiCorp must adjust this on their end.