poshbotio/PoshBot v0.11.2

on GitHub

[0.11.2] 2018-10-11

Added

• Specifying the contents of a file to upload, as well as its file name and type are now supported in New-PoshBotFileUpload.
  This is in addition to the already supported feature of specifying a file path.

Changes

• #122 Enable running multiple versions of PoshBot side-by-side. When PoshBot needs to load itself (via running PoshBot as a job, a scheduled task, or a plugin command), it now loads the exact version of PoshBot that is currently running instead of loading the latest version that happens to be in $env:PSModulePath. This enables multiple versions of PoshBot to be running and be self-contained. (via @Tadas)

Fixed

• When starting PoshBot using Start-PoshBot -AsJob, determine the correct backend instance to create by validating the passed in configuration against the names Slack, SlackBackend, Teams, and TeamsBackend.

• ChannelRules in the bot configuration were not being serialized correctly if more than one hashtable entry was present.

• Match documentation and check for SlackBackend or TeamsBackend backend names when starting PoshBot as a PowerShell job.

• #111 Use CommandParser to strip out extra line breaks from a message received from Teams (via @AndrewPla)

• Resolve ambiguous method signature error in Slack backend by using an [ArraySegment[byte[]] buffer in the System.Net.WebSockets.ClientWebSocket.ReceiveAsync() method.

• #125 Escape prefix character when evaluating messages.
  Any single character can be defined as the prefix character (default is "!") that indicates to PoshBot that the incoming message is a bot command. Some of these characters are also regex special characters and we need to escape them properly so when people indicate they want to use the '.' or '^' characters for example, they are treated a literal. (via @Windos)

• Fix bot crash when removing a scheduled command that was configured to only trigger once.

• #121 Prevent multiple executions of commands scheduled in the past. This fixes an issue where if the StartAfter value of a scheduled command was in the past, on bot startup the scheduled command would be executed however many intervals difference there was between the StartAfter value and the current time. (via @AngleOSaxon)

• HTML decode the message text received from the backend. This ensures characters like '&' are converted back from their encoded version '&' that may have been received.