Release notes - Self-Hosted versions
Last updated
Last updated
New
It's now possible to copy practices from a space to another, which include all the source code examples. See more here.
Packmind now integrates with Git repositories hosted on Bitbucket Data Center.
It's now possible to ask AI to generate a new description for a coding practice.
Improved
The quality of the results generated by AI (coding practices and questions) has been improved for OpenAI and Azure OpenAI.
Several minor improvements within the practice review module
Fixed
Fix an issue with the validation of Semgrep patterns when Packmind runs in offline context
Upgrade Docker Images to 5.1.0 or Upgrade the Helm Chart to 1.1.0
This is the first release of Packmind with its new identity (previously known as Promyze).
A completely rebranded UX and UI
A dedicated module for AI suggestions including a smoother navigation in the results
Improve logs on Git integrations and Azure OpenAI integrations.
Fix an issue with the Docker container that runs Packmind in a single container
Packmind leverages AI capabilities to serve generative coding practices, assisting Tech leaders with suggestions on how to improve code and question the technical choices made by developers.
Packmind AI offers continous generation of coding practices and discussion topics using the integration with Git repositories. Packmind AI scans your latest code changes to suggest new material for your next practice review workshop. This AI analysis can also be run within our IDE plugins on a specific file.
Here is an example of generad practice, that drivers must validate or not for the next practice review:
Packmind AI will also generate textual description for your coding practices along with regular expressions for their automatic detection.
Behind the scenes, Packmind AI relies on one of the following LLM:
OpenAI managed by Packmind (Cloud only)
Your own OpenAI instance
Your Azure OpenAI instance
Note that Packmind AI is not enabled by default, you should first enable it. Also, it's possible to disable AI for specific spaces to meet your legal constraints.
You can get started with Packmind AI by reading the docs.
If your coding practices must be illustrated with code examples scattered on different files, multi-file examples come to the rescue. They are particularly relevant for coding practices related to design or architecture. You can attach a series of code examples and add a textual description to each single example.
Here is an illustration of a coding practice with two positive examples:
Multi-file examples can be managed directly through the UI using existing examples or use the following Packmind IDE extensions (read the associated doc here):
Packmind extension for VSCode: 8.1.1 or higher
Packmind extension for JetBrains: 7.1.0 or higher
Packmind extension for VS: 5.2.0 or higher
Packmind extension for Eclipse will be released soon by the end of 2023.
The hour of the day at which the Git scheduler runs can be tuned through the GIT_AI_SCHEDULER_HOUR environment variable on promyze-api container (use a number between 0 and 23).
The hour of the day at which the practice scheduler runs can be tuned through the PRACTICE_SCHEDULER_HOUR environment variable on promyze-api container (use a number between 0 and 23).
It's now possible to test the emails sent through the practice schedulers.
The public REST API route that retrieves the coding practices for a space now returns the categories in plain text instead of the ID references.
Helm Chart: 0.5.0
Several vulnerabilities (CVE) have been fixed.
Drivers stand for Tech Lead, Lead Dev, or anyone organizing and leading the practice review workshops. They are expected to be core contributors in Packmind for coding practices and discussion topics. Other developers will be Contributors, meaning they're expected to submit contributions occasionally.
Each user is now either a Driver or a Contributor in Packmind. You'll be asked to choose your role on your next sign-in.
You can now connect your GitLab, GitHub, Azure DevOps, and BitBucket platform to get an overview of recent code modifications and to identify coding practices and discussion topics for the next practices review workshop.
The review preparation module lists recent pieces of code and offers many filters to tune the scope (files, authors, date, …). You can quickly generate material for the next practice review workshop in a few minutes.
Learn how to connect your Git platform to Packmind in 1 min.
Each space can now configure a scheduler that will push coding practices directly to users in the space, either daily, weekly, or monthly. Packmind can automatically selects a practice to send, but Drivers can also feed the queue with specific practices. Think of this feature as an internal newsletter or reminders sent to the team. Here is an example of a notification sent on Slack:
Learn how to enable the scheduler here.
The Data Board has been redesigned to provide a more precise overview of how your teams use Packmind and what benefits you get from it.
If you already have documented existing coding practices in a wiki tool (such as Confluence or Notion), you can now use the latest Packmind Web browser plugin to import them into Packmind. Read more on the docs.
We now offer a module to export your coding practices into a single Markdown file. Read more here.
