Meltano v1.26.1 and v1.26.2 are Now Available

Meltano version 1.26.1 is now available, with a more focused and less broad set of supported data sources on hosted instances, and improved support for date range filters on embedded reports and dashboards.

Meltano version 1.26.2 fixes a regression introduced in v1.26.1.


  • #1854 Remove non-marketing-sales data sources from UI
  • #1881 Store in system database when user was last active
  • #1846 Freeze reports with relative date filters in time when shared or embedded
  • #1847 Show date range on embedded reports and dashboards
  • #1847 Show date range on reports on dashboards

Meet the team: Douwe

As you’re getting to know Meltano, and as we are getting to know you and your company’s needs, we thought it would be appropriate for you to also get to know our team a little bit better!

And for the moment, that team is me: Douwe Maan.

I was born and raised in the Netherlands, currently live in Mexico City, and started working at GitLab a little over 5 years ago. Meltano, as you might know, is a project of GitLab, being operated as an internal startup.

I joined GitLab as a developer straight out of college when the company was just 10 people in size (we’re 1200+ now, in 67 different countries!). A few months later, I was tasked with hiring more developers, and once the team had doubled in size of couple of times and we started to run into the limitations of the flat organizational structure at scale, I became the first Development Lead.

Over the following years, the product and engineering organizations continued to grow, and existing teams were split up and new teams were created. The name of my team and the scope of its responsibility changed roughly every 9 months, until we were left with what I like to think of as GitLab’s core functionality: Source Code Management, pretty much everything related to managing and exploring Git repositories and collaborating using merge requests.

Since this had always been the part of GitLab dearest to my heart, it was great to now have a full team dedicated to it: more people working on improving the features in this area than had been at the entire company when I originally came on board.

By this point, though, the tiny startup I had joined 4 years before had grown 100x and was now a serious tech company; still an amazing and positively unique place to work, but quite a different beast than what I had initially been attracted to. With my team now finally dedicated to nothing but my favorite part of GitLab, I felt like my time in GitLab’s engineering organization had reached its natural final chapter, and I started thinking about what I would like the next chapter to say.

And that’s where Meltano came in: an internal startup at GitLab, working remotely and according to the GitLab values, but with a totally different product area and tech stack, and a team of just 5 people, that was looking for someone to lead and strengthen its engineering team. In other words, a match made in heaven for me: an opportunity to take everything that I had learned about engineering at startups, 1000-people tech companies and everything in between, and to use it to help grow what had (and has!) the potential to be GitLab’s second major product.

And so, in September 2019, I left GitLab’s engineering organization (but not the company) and joined General Manager Danielle, Backend Engineers Yannis and Micael, and Frontend Engineers Derek and Ben at Meltano.

After 6 months on the team, it was decided earlier this month that Danielle and the others would start looking for other opportunities inside GitLab (and out) where their skills and experience are in higher need right now, with me remaining on and leading the Meltano project solo for the time being.

I have tremendously enjoyed working with and learning from all of them, and I am honored and humbled to be given the opportunity to carry this project and their contributions forward on a path that was started by them and others long before I came on board and that we have continued to refine together over time.

While we haven’t quite been able to find product-market fit yet, we have experienced significant interest from startup founders all around the world and are working closely with them every day to find out where and how we can deliver the most value to help them run and find success with their businesses.

If you would like to see your startup sales funnel, analyzed, and are interested in a single set of dashboards and reports for the entire journey from ad impression to website visitor to successful sale to help you figure out what works, what doesn’t, what to scale up, and what to ramp down, please give Meltano a try, and don’t hesitate to get in touch if there is anything I can do to improve your experience!

Meltano v1.26.0 is Now Available

Meltano version 1.26.0 is now available, with various improvements and bug fixes.

If your Meltano instance is hosted on, it will have been upgraded automatically. For instructions on upgrading a self-hosted installation, check out the documentation.


  • #1188 Allow sorting by timeframe period columns (e.g. “Creation Date: Month”, “Creation Date: Year”)
  • #1873 Display error message when viewing model/design/report before pipeline has run
  • #1874 Print full error when initial model compilation fails
  • #1875 Automatically run query when sorting is changed
  • #1876 Don’t store Analyze UI state in report file
  • #1877 Allow designs to reference the same table more than once
  • #1878 Recompile models when meltano is upgraded

Meltano v1.25.1 is Now Available

Meltano versions 1.25.1 is now available, with various UX improvements and bug fixes.

The changelog below also lists new features and other changes introduced in v1.24.1 and v1.25.0, since these were not announced in their own blog posts.


  • #1799 Improve date range UX by displaying the date range associated with each attribute in the <select> (previously the user had to manually check each one-by-one to see if it had an associated date range filter)
  • #1843 Update the Google Ads Extractor selected attributes definition to also extract the Ad Network and Device segments for the Ads Performance Reports.
  • !1523 Add support for relative date filter definitions to Meltano Filters. That means that filters over dates and times can have a [+-]N[dmy] format instead of a fixed date. That allows Meltano to generate a date relative to a pivot date provided by in the query definition or NOW().
  • #1830 Add relative vs. absolute date ranges to date range picker of Report Builder


  • #1799 Update “Date Range(s)” button label to account for pluralization
  • #1799 Fallback to inline text and only display the date range <select> if there are two or more date ranges to filter on
  • #1799 Update date range picker to initialize at the first attribute with a valid date range
  • #1799 Update the Report Builder’s “jump to date range dropdown” buttons (small calendar icon button associated with the left pane’s attribute items) to automatically focus the date range that’s associated
  • #1852 Move Pipelines after Connections in navbar
  • #1850 Rename Connections tab “Connection” and “Pipeline” buttons to “Edit Connection”, and “View Pipeline”
  • #1856 Remove “Custom” data source option from UI
  • #1867 Make timeframe table headings more human-friendly
  • #1830 Update date ranges calendars with “Today” marker for improved UX


  • #1872 Delete state left over from different pipeline run for same extractor
  • #1779 Fix loading report directly by URL when design request completes before reports request
  • #1848 Fix Explore page “Report Builder” column loading when model name and model topic name do not match

Meltano Permissions is now Permifrost

As Meltano continues to iterate towards product-market fit, we decided to remove a part of the codebase that no longer fit our target persona. Meltano previously had a command line tool for managing permissions on a Snowflake data warehouse. This is now a separate Python package managed by the GitLab Data Team: Permifrost.

As a separate package, Permifrost is now installable via pip. It is currently on version 0.1.0 and will continue to be regularly updated and improved as the GitLab Data Team continues to use it.

It is fully open-sourced under an MIT license and we hope the Snowflake community will use and contribute to it. Issues can be made in the main Permifrost project.

Meltano v1.24.0 is Now Available

Meltano version 1.24.0 is now available, with a new “Explore” dropdown in the navigation bar, and fixes for a handful of bugs.


  • #1831 Change main navigation “Reports” to “Explore” and update its nested CTAs to link to a landing page per data source
  • #1705 Remove meltano permissions feature now that it has been extracted into
  • Updated “Report Builder” page with a header to better communicate what the page is for.


  • #1840 Format InputDateIso8601 value as YYYY-MM-DD since a full timestamp value could represent a different date in UTC and local timezone
  • #1842 Fix empty filter attributes bug for non-join designs

Meltano v1.23.2 is Now Available

Meltano versions 1.23.2 is now available, with a new chart type and fixes for a handful of bugs.


  • #1820 Add Vertical Bar chart type to Report chart options


  • #1820 Updated chart type selection as a dropdown for improved UX (ensures the chart icon is adorned with its label)


  • #1836 Don’t crash when gunicorn is sent HUP signal to reload Meltano service
  • #1837 Fix tap-mongodb database name setting
  • #1838 Properly handle dates and timezones in date range picker
  • #1838 Ensure records on boundary dates are included when using date range picker with column of type “time”