-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI tooling update #239
Comments
@coryasilva, great idea! Please see: #238. I'm no longer maintaining this project. Would you like to become a maintainer? If so, please work with @revmischa. Thank you! |
@bestickley Oh I missed that, thanks. I do find value in consolidating our efforts. Your new repo addresses my main pain points of open-next and compliance. Also glad you added aws-nag -- I have sooooo many overrides using this impl to meet compliance. lol. @revmischa are you looking for maintainers? I am interested in maintaining this. (In the meantime I plan on using this repo for a couple production site, I am also completely okay just using my forked code either way) |
@coryasilva, yeah I agree it's not ideal to have 2 CDK Next.js projects, but I wanted to get away from open-next (for simplicity and reasons explained in README) and that would have been too big of a change to propose here. |
Certainly! You're welcome to take it over. Hit me up on discord |
Github artifact actions v3 going away in Jan 2025. Consider updated to projen >=0.87
projen/projen#3820 (comment)
https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
@bestickley BTW do you think we can get rid of the manual build approvals on this repo?
The text was updated successfully, but these errors were encountered: