Yep. Said another way: The archetype is simply a convenient starting point to build out boilerplate file structure. It's convenient, but still requires some fundamental understanding on how Maven works.
The archetype isn't frequently updated because the structure of the boilerplate code doesn't really change across minor ignition releases. The version of ignition is not a meaningful part of the archetype, as it's expected that you'll update that regularly for development, testing and releases, just as you would any other dependency.
So don't worry too much about the version of the archetype, just update the versions you want to build against as appropriate.