v7.0.0-beta.1

• Grammy migration (#166) 0231fba

v6.3.0...v7.0.0-beta.1

v6.3.0

• feat(body): add InvoiceBody 955dec8

v6.2.1...v6.3.0

v6.2.1

• fix: adapt to new internal typing locations f7fb05c

Somewhat breaking: requires telegraf v4.3

v6.2.0...v6.2.1

v6.2.0

• feat(template): add manualAction 3d2e6e7
• fix(middleware): improve detection of bad rootTriggers cd23a88

v6.1.0...v6.2.0

v6.1.0

• refactor(send-menu): improve return type of edit functions ed79741

v6.0.0...v6.1.0

v6.0 - Migrate to telegraf v4

• migrate to telegraf v4

v5.3.0...v6.0.0

Migrate from version 5 to version 6

Version 6 switched from telegraf 3.38 to 4.0. See the telegraf migration guide for this set of changes.

telegraf-inline-menu is relativly unaffected by this.
The only change required besides the telegraf changes is the change of ctx.match.
Simply add match to your MyContext type:

export interface MyContext extends TelegrafContext {
	readonly match: RegExpExecArray | undefined;
	…
}

telegraf knows when match is available or not.
The default Context does not have match anymore.
telegraf-inline-menu should also know this in a future release.

v6.0.0-alpha1

• feat: migrate to telegraf v4 3a2698f

Known issue: context.match typings are not available like they are when using bot.action(context => { console.log(context.match); }.
Check details in #144

v5.3.0...v6.0.0-alpha1

v5.3.0

• feat(choices): allow usage of Map<number, string> 83b0d3b
• fix(choices): readonly record 8c8c6d5

v5.2.1...v5.3.0

v5.2.1

• chore(npm): using types is a dependency d495d9b

v5.2.0...v5.2.1

v5.2.0

• feat(body): add LocationBody and VenueBody 26348af

v5.1.0...v5.2.0