Tweag, the OSPO of Modus Create

We’re at Team '25 and are excited to announce that Modus Create has been named a winner of the Atlassian Partner of the Year 2024-2025 in the AI Innovation category! 🏆 This award honors our contributions to Atlassian customers throughout 2024, showcasing our team's innovation, expertise, and dedication to delivering transformative solutions. 👏 For the fourth consecutive year, Atlassian has recognized Modus Create as a Partner of the Year for exceptional Atlassian services. 🎉 Learn more 👉 https://hubs.ly/Q03gmc740 #Atlassian #AtlassianTeam25 #Team25 #AI #Innovation

📣 New release: linear-base 0.5.0, with a decent chunk of bug fixes and interface improvements. Some of these should have had a release a while ago, our apologies about that. See the full change log at https://lnkd.in/eR6-97D9 .

📣 Big Topiary news! Topiary's documentation is now assembled in a structured website, the Topiary Book, instead of being a giant README file on Github. We hope you'll find it useful.

📣 A new version of Liquid Haskell is out, featuring the work of several contributors to improve the proof mechanisms, support for CVC5 and more. In his new blog post, Facundo Domínguez takes you on a tour of the highlights!

Our Scalable Build Group has just published issue 28 of their build //newsletter. Subscribe for updates on the latest developments in the build system space: https://hubs.ly/Q03cws3K0 #opensource #software #engineering

GW OSCON is happening next week in Washington DC, and our own Richard Bullington-McGuire will be talking on Tuesday the 25th of March about DevOps in service of winter cycling 🥶. Registration close super soon, so register now.

FawltyDeps v0.19.0 released, with multiple highlights: - We finally have a proper documentation website, at https://lnkd.in/eGkWKbt7! 🎉 Our README was growing very long, and thanks to our own https://lnkd.in/eHGsBmWX , this is now split up and reorganized according to Diátaxis principles. - Next, we now support PEP 735 , aka. the new optional [dependency-groups] section in your pyproject.toml. For now, dependency declarations in this section are treated the same as other dependency declarations, that is, FawltyDeps will expect to find import's in your code that correspond to these dependencies. - Finally, this release introduces support for Python v3.13 and drops support for Python v3.7. We are slowly moving to a policy of only supporting actively maintained Python versions, and this release will be the last to support Python v3.8. If your project is stuck on an older Python version, we suggest installing FawltyDeps stand-alone (and not as a development dependency inside your project's environment). If this somehow does not work for you please raise a new issue (or comment on issue #460), and we'll try to help you out. Alternatively, for projects using Python v3.7, you can of course use an older FawltyDeps version as long as that works for you. Full release notes at https://lnkd.in/e_2pvPND #fawltydeps #python

Create React App has just been officially deprecated https://lnkd.in/d2cJYXAC . They say to migrate to a framework like next.js, or a high-performance build tool like Vite or Parcel. As it happens, our own Edian Comachio wrote a blog post just a few months ago on the benefits of Vite—especially in terms of developer experience and performance—with benchmarks and everything https://lnkd.in/eV3uUxxK . Read it and let us know if it helps. #cra #createreactapp #vite

In their new blog post about Bazel and Testwell CTC++ https://lnkd.in/e6bjHATn Johan Herland and Mark Karpov share a good example (or maybe a cautionary tale 😉) of how to take a tool that does not play well with Bazel’s idea of a well-behaved build step, and force it into a shape where we can still leverage Bazel’s strengths. #bazel #testing #coverage #testwellctc

Quick update. For a few hours a post was up from us on some dodgy looking Solana asset. We are still auditing on who or what was compromised on our end. BUT THIS POST WAS NOT FROM US. Please don't engage.