Skip to content

v1.1.0 -- Legacy "Theme" Release
Compare
Choose a tag to compare
@zetlen zetlen released this 27 Sep 16:24
v1.1.0
b2d6757
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

This is intended to be the final "minor" release on the existing PWA Studio architecture. Those who are working on projects currently based on master can continue to open pull requests against master if they are hotfix-sized changes, meaning that they fix bugs or performance issues, and do not change any public APIs or expected behaviors.

Significant Changes

There is no established prior release to which to compare, so this changelog reflects a diff of the last month of merged changes.

  • chore(cicd): Removed Greenkeeper to increase test coverage before automating package updates
  • chore(community): Added Community Contributors
  • chore(cicd): Switched Lerna to "fixed" mode so all packages share a version
  • feat(dev): Added root-level NPM scripts to ease common development modes
  • chore(dependencies): Refactored developer dependencies to root as much as possible
  • fix(compat): Changed Babel settings to address later browsers
  • cleanup(peregrine): Removed unused Peregrine Simulators
  • fix(peregrine): Handled absence of Error.captureStackTrace
  • refactor(buildpack): Refactored PWADevServer to make SSL and hostnames optional and generate hostnames differently
  • fix(buildpack): Fixed duplicated dependencies bug in MagentoRootComponentsPlugin
  • fix(buildpack): Added better error reporting for SSL cert generation problems
  • docs(peregrine): Added documentation for Peregrine utilities and components
  • docs(buildpack): Added documentation for Buildpack utilities, specifically PWADevServer
  • docs: Added Basic Concepts documentation for CSS Modules
  • docs(venia): Updated Venia setup docs
  • feat(venia): Added browser-routed Link elements to navigate between pages
  • chore(venia): Adjusted Webpack config for clearer reporting

Acknowledgments

Thanks to all our community contributors, core engineers, documenters, and managers for helping us to formalize our process and take the next big step.

Assets 2
Loading