You don't. An issue is either done, or you're still working on it.
Kanban is not really that focussed on distinct and discrete release packaging. The giveaway in your question here is you've mentioned "sprint". If you're doing Sprints, you're not doing Kanban. I suspect your only option is to release as per Scrum or Kanban, whichever suits you better and then have someone add package versions later (or before, if you do it as a custom field instead of a version)
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG